Hi Thilo,
Here are some small explanations of what each option does
-r: specifies the repository against which the code is generated...
What effect does this have on the result? When would this be
useful or what's the use case?
The usecase for this is codegenerating with a WSDL that has WS-Policy
statements. When you have policy statements the system should know
what the assertions are and how to deal with them. This is done by
using the modules in a repository and hence a repository needs to be
pointed out. This has no effect if you don't have any WSP entries in
your WSDL.
-em: this is to specify an external mapping file. For what kind
of mapping?
External databinding mappings. There has been numerous cases where
users wanted to use the classes they already have (say the XMLBeans
classes they've already generated seperately) rather than codegen
generating them. The mapping file is an xml file in the following
format
<mappings dbf="adb">
<mapping>
<qname namespace="ns" prefix="p1">localName</qname>
<value>type</value>
</mapping>
</mappings>
Note that the mapping element can be repeated.
So basically the system picks up classes that are specified rather
than generating them. However you can specify only the ones that you
want to replace where the system will generate the rest.
- uw: switches on unwrapping. Of What? Does this refer to wrapped
SOAP message style? Where can I find an example?
I guess Dennis gave a good explanation of this. ADB unwrapping indeed
works but it may 'glitch' in some extreme cases. Anyway the
noticeable change for the user is the change in the method signature.
-b: I can see what this option is doing, but what is the actual
purpose of it??
Backward compatibility flag. This basically drills down to the naming
of the classes that are generated. When the flag is on, the generated
class names are compatible with the Axis 1.x style ( that is why its
called backward compatible flag :))
I also found that the official User Guide documents different sets
of options for the command-line tool and the Ant task. Both sets
are again different from the set of options that is diplayed in
the usage information when invoking WSDL2Java at the command-line.
This should be consolidated.
Yes I agree. This is another classic case of documentation being slow
in synchronizing with the changes in the code. I'm tied till thursday
this week but I'll see whether I can clear things up by the weekend.
(Unless of course somebody else jumps up and finishes it before then
;))
Thanks,
Thilo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
