Hi, this seems to occur when the WSDL has XML schema restrictions and you
then run wsdl2java with the default ADB binding. It seems the type1 classes
are wrappers that enforce the XML schema restrictions in the setters.
One way to work around this is create your own Java beans and use JiBX data
binding. However there is significant amount of work and learning when using
a different data binding.
Steve Cohen wrote:
>
> running command line WSDL2Java, (axis2 1.4.1) with following options
>
> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion
> 1.5 -uri {my wsdl}
>
>
> I find the following source code generation pattern:
> In reasonable packages under source, it generates data classes from the
> WSDL, say com.whatever.City1.java
> com.whatever.State1.java
>
> But it also generates (in the default package)
> City0.java
> State0.java
>
> What could be causing it to generate these extra classes in the default
> package and is there anything I can or should do about it.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/WSDL2Java-behavior-tp19744185p19771435.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
