Eclipse Plugin: Usage

# Eclipse Plugin: Usage |

JiBX Basics Overview Getting Started Binding Compiler Binding on Load Runtime Extras Building JiBX Contributing License News and Status Support FAQ Mailing Lists Bugs User Comments Sponsors Start from Code Start from Code BindGen Example Code Example 1 Example 2 Example 3 Example 4 Customizations Reference SchemaGen Jibx2Wsdl Examples Customizations Start from Schema Start from Schema CodeGen Example Code Example 1 Example 2 Example 3 Customizations Reference Binding Definition Binding Tutorial A basic binding Binding extras Structure mapping Collections and arrays Using mappings Advanced binding Method hooks Custom code Precompiled Bindings Definition details Definition contexts Conversions XML summary <binding> element <include> element <format> element <namespace> element <mapping> element <value> element <structure> element <collection> element Attribute groups Usage API Runtime JavaDocs Subprojects Eclipse Plug-in Introduction Install Usage Axis2 Usage | ### Using the org.jibx.eclipse Plug-in #### Create Java Project Create a Java project project1 using the project wizard. #### Enable JiBX Enable the JiBX plugin for project1. #### JiBX Properties At the project level are the following JiBX properties: JiBX Mapping Folder: Location where mapping files are stored. Verbose compilation: Usefull for seeing what the binding compiler is up to The location of src/main/config is chosen by default to match the (non-Eclipse based) Maven plugin maven-jibx-plugin, so you would then want a Mavenish classpath like this: #### Done The plugin will parse all xml files contained in your mappings folder to identify which java classes require bindings. The JiBX binding process itself is a full binding of all bound classes every time(ie, there is no such thing as incremental JiBX binding). The plugin is invoked by Eclipse whenever A "full compilation" (Project->Clean) of the workspace is performed Any bound java file is modified/saved Any mapping file is modified/saved A new mapping file is added to the mapping folder Any one of the previous events cause the plugin to re-bind all classes in the project The plugin allocates a new Eclipse console that will display details of the plugin operation