abstract class BaseAxisConfig extends java.lang.Object
| Type | Name and description |
|---|---|
boolean |
generateTestcaseGenerate a client-side JUnit test case. |
java.lang.String |
nameName of the config. |
java.util.Map<java.lang.String, java.lang.String> |
namespacePackageMappingBy default, package names are generated from the namespace strings in the WSDL document in a magical manner (typically, if the namespace is of the form "http://x.y.com" or "urn:x.y.com" the corresponding package will be "com.y.x"). |
java.io.File |
namespacePackageMappingFileIf there are a number of namespaces in the WSDL document, listing a mapping for them all could become tedious. |
java.lang.String |
packageNameThis is a shorthand option to map all namespaces in a WSDL document to the same Java package name. |
java.io.File |
wsdlFileWSDL file for processing. |
| Constructor and description |
|---|
BaseAxisConfig
(java.lang.String name) |
| Methods inherited from class | Name |
|---|---|
class java.lang.Object |
java.lang.Object#wait(long, int), java.lang.Object#wait(long), java.lang.Object#wait(), java.lang.Object#equals(java.lang.Object), java.lang.Object#toString(), java.lang.Object#hashCode(), java.lang.Object#getClass(), java.lang.Object#notify(), java.lang.Object#notifyAll() |
Generate a client-side JUnit test case. This test case can stand on its own, but it doesn't really do anything except pass default values (null for objects, 0 or false for primitive types). Like the generated implementation file, the generated test case file could be considered a template that you may fill in.
Name of the config.
By default, package names are generated from the namespace strings in the WSDL document in a magical manner (typically, if the namespace is of the form "http://x.y.com" or "urn:x.y.com" the corresponding package will be "com.y.x"). If this magic is not what you want, you can provide your own mapping using the this maps argument. For example, if there is a namespace in the WSDL document called "urn:AddressFetcher2", and you want files generated from the objects within this namespace to reside in the package samples.addr, you would provide the following option:
urn:AddressFetcher2=samples.addr
If there are a number of namespaces in the WSDL document, listing a mapping for them all could become tedious. To help keep the command line terse, WSDL2Java will also look for mappings in a properties file. By default, this file is named "NStoPkg.properties" and it must reside in the default package (ie., no package). But you can explicitly provide your own file using this option. The entries in this file are of the same form as the arguments to the namespacePackageMapping option. For example, instead of providing the command line option as above, we could provide the same information in a properties file:
(Note that the colon must be escaped in the properties file.) If an entry for a given mapping exists both with namespacePackageMapping and in this properties file, the namespacePackageMapping entry takes precedence.urn\:AddressFetcher2=samples.addr
This is a shorthand option to map all namespaces in a WSDL document to the same Java package name. This can be useful, but dangerous. You must make sure that you understand the effects of doing this. For instance there may be multiple types with the same name in different namespaces. Only for Axis1: It is an error to use the --NStoPkg switch and --package at the same time.
WSDL file for processing.
Groovy Documentation