Full name:
org.jibx:jibx-maven-plugin:1.3.3:test-jibx2wsdl
Description:
Attributes:
| Name | Type | Since | Description |
|---|---|---|---|
| <interfaceClassNames> | ArrayList | - | The full class names of the service interface. Note: Classes
should be in target/classes (which is where they should be after
compiling). User property is: interfaceClassNames. |
| <load> | boolean | - | Control flag for test loading generated/modified classes. Default value is: false. User property is: load. |
| <multimodule> | boolean | - | Control flag multi-module mode. Default value is: false. User property is: multi-module. |
| <outputDirectory> | String | - | Target directory path for generated output (default is current
directory). Note: If you want the wsdl and schema included
in your distribution, remember to include it in the
<resources> section of your pom file. Default value is: ${project.build.directory}/schema. User property is: outputDirectory. |
| <validate> | boolean | - | Control flag for test loading generated/modified classes. Default value is: true. User property is: validate. |
| <verbose> | boolean | - | Control flag for verbose processing reports. Default value is: false. User property is: verbose. |
| <verify> | boolean | - | Control flag for verifying generated/modified classes with BCEL. Default value is: false. User property is: verify. |
| Name | Type | Since | Description |
|---|---|---|---|
| <baseBindingDirectory> | String | - | Get the default location of the base binding files. Defaults value is: schemaBindingDirectory. User property is: baseBindingDirectory. |
| <customizations> | ArrayList | - | Include pattern for customization files. User property is: customizations. |
| <directory> | String | - | Deprecated. - Since binding and codegen use this for different locations, use
schemaBindingDirectory. Defaults to "src/main/config" (or "src/test/config" for test goals). User property is: directory. |
| <excludeSchemaBindings> | ArrayList | - | Exclude pattern for schema binding files. User property is: excludeSchemaBindings. |
| <excludes> | ArrayList | - | Deprecated. - This name was confusing since it is used as a binding file
pattern for bind and a schema file pattern for code-gen. Use excludeSchemaBindings for binding and excludeSchemas for schema User property is: excludes. |
| <includeBaseBindings> | HashSet | - | A list of modules or files to search for base binding files. This
can specify files in the local directory or files stored in your
dependencies. If your based binding files are in a local file
system, specify them as follows: <includeBaseBindings> <includeBaseBinding> <directory>src/main/config</directory> <includes> <include>base-binding.xml</include> </includes> </includeBaseBinding> </includeBaseBindings> If your based binding files are in a artifact that is one of your dependencies: <includeBaseBindings> <includeBaseBinding> <groupId>com.mycompany.baseschema</groupId> <artifactId>base-schema</artifactId> <classifier>bindings</classifier> <directory>META-INF</directory> <includes> <include>base-binding.xml</include> </includes> </includeBaseBinding> </includeBaseBindings> The classifier is optional (if your binding file is not in the main artifact) A version is not necessary, since this declaration must be on your list of dependencies. Note: For file filters, use the standard filter format described in the plexus DirectoryScanner. Defaults value is: binding.xml. Include existing bindings and use mappings from the bindings for matching schema global definitions. (this is the basis for modular code generation) Note: If directory is not specified, relative paths start at <baseBindingDirectory>. User property is: includeBaseBindings. |
| <includeSchemaBindings> | ArrayList | - | Include pattern for schema binding files. Note: Uses the standard filter format described in the plexus DirectoryScanner. Defaults value is: binding.xml. Include existing bindings and use mappings from the bindings for matching schema global definitions. (this is the basis for modular code generation) Include base bindings as follows: <includeSchemaBindings> <includeSchemaBinding>base-binding.xml</includeSchemaBinding> </includeSchemaBindings> Note: Relative paths start at <directory>. User property is: includeSchemaBindings. |
| <includes> | ArrayList | - | Deprecated. - This name was confusing since it is used as a binding file
pattern for bind and a schema file pattern for code-gen. Use includeSchemaBindings for binding and includeSchemas for schema. Note: Uses the standard filter format described in the plexus DirectoryScanner. Defaults value is: binding.xml. User property is: includes. |
| <modules> | HashSet | - | A list of modules to search for binding files in the format:
groupID:artifactID User property is: modules. |
| <options> | Map | - | Extra options to be given for customization via CLI.Enter extra
customizations or other command-line options. The extra customizations are described on the JiBX2WSDL customizations page The single character JiBX2WSDL commands may also be supplied here. For example, to include Names of extra classes (-x) and Sets the base address used for the service endpoint address specified in the WSDL, supply the following options: <options> <x>com.company.pacakge.ClassName</x> <service-base>http://localhost:8080/axis2/services</service-base> </options> |
| <schemaBindingDirectory> | String | - | The directory which contains schema binding files. Defaults to
"src/main/config" (or "src/test/config" for test goals). For
code-gen or if the default directory does not exist, defaults to
"target/generated-sources" (or "target/generated-test-sources" for
test goals). User property is: schemaBindingDirectory. |
| <sourceDirectories> | ArrayList | - | The source directories. Note: The source directory defaults
to: <sourceDirectories> <sourceDirectory>src/main/java</sourceDirectory> </sourceDirectories> If you are using the code-gen plugin, you may want to specify the generated sources directory: <sourceDirectories> <sourceDirectory>src/main/java</sourceDirectory> <sourceDirectory>${project.build.directory}/generated-source</sourceDirectory> </sourceDirectories> If you don't want sources include, you will have to explicitly delare an empty list: <sourceDirectories> <sourceDirectory></sourceDirectory> </sourceDirectories> User property is: sourceDirectories. |