Re: WSDL2Java behavior
You might wanna use the -uw option (Unwrap) which generates better method
signatures for you.
Thanks,
Keith.
On Wed, Oct 1, 2008 at 9:59 PM, Steve Cohen <[EMAIL PROTECTED]> wrote:
> Any luck in figuring out why this WSDL generates such gnarly code? It is a
> real pain to work with all these nested objects that WSDL2Java created for
> me. What should be simple setters and getters are a nightmare.
>
>
>
> Steve Cohen wrote:
>
>> I'm not sure. I now see that each xxx_type1 class uses the xxx_type0.
>>
>> In any case, the WSDL in question is available here:
>>
>> https://duoshare.com/dsWS/services/PostML/wsdl
>>
>>
>> Martin Gainty wrote:
>>
>>> Good Morning Mr Cohen
>>>
>>> there appears to be a double definition for City and State entities
>>> can you display the WSDL so we can reproduce here?
>>>
>>> thanks
>>> Martin
>>> __
>>> Disclaimer and confidentiality note
>>> Everything in this e-mail and any attachments relates to the official
>>> business of Sender. This transmission is of a confidential nature and Sender
>>> does not endorse distribution to any party other than intended recipient.
>>> Sender does not necessarily endorse content contained within this
>>> transmission.
>>>
>>>
>>> > Date: Tue, 30 Sep 2008 10:16:14 -0500
>>> > From: [EMAIL PROTECTED]
>>> > To: axis-user@ws.apache.org
>>> > Subject: WSDL2Java behavior
>>> >
>>> > 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]
>>> >
>>>
>>>
>>> Stay up to date on your PC, the Web, and your mobile phone with Windows
>>> Live. See Now <
>>> http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: WSDL2Java behavior
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]
Re: WSDL2Java behavior
Any luck in figuring out why this WSDL generates such gnarly code? It
is a real pain to work with all these nested objects that WSDL2Java
created for me. What should be simple setters and getters are a nightmare.
Steve Cohen wrote:
I'm not sure. I now see that each xxx_type1 class uses the xxx_type0.
In any case, the WSDL in question is available here:
https://duoshare.com/dsWS/services/PostML/wsdl
Martin Gainty wrote:
Good Morning Mr Cohen
there appears to be a double definition for City and State entities
can you display the WSDL so we can reproduce here?
thanks
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained
within this transmission.
> Date: Tue, 30 Sep 2008 10:16:14 -0500
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: WSDL2Java behavior
>
> 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]
>
Stay up to date on your PC, the Web, and your mobile phone with
Windows Live. See Now
Re: WSDL2Java behavior
I'm not sure. I now see that each xxx_type1 class uses the xxx_type0.
In any case, the WSDL in question is available here:
https://duoshare.com/dsWS/services/PostML/wsdl
Martin Gainty wrote:
Good Morning Mr Cohen
there appears to be a double definition for City and State entities
can you display the WSDL so we can reproduce here?
thanks
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained
within this transmission.
> Date: Tue, 30 Sep 2008 10:16:14 -0500
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: WSDL2Java behavior
>
> 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]
>
Stay up to date on your PC, the Web, and your mobile phone with
Windows Live. See Now
RE: WSDL2Java behavior
Good Morning Mr Cohen
there appears to be a double definition for City and State entities
can you display the WSDL so we can reproduce here?
thanks
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Tue, 30 Sep 2008 10:16:14 -0500
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: WSDL2Java behavior
>
> 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]
>
_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
RE: wsdl2java behavior for multiple services in the same wsdl
Title: RE: wsdl2java behavior for multiple services in the same wsdl Just in case others try to do same thing : I had to run the wsdl2java for each service in the wsdl file, using the -sn option, to be able to generate code for *all* the services in the wsdl file. Gul _ From: Onural, Gul (CAR:SI12) Sent: Friday, October 20, 2006 9:51 AM To: axis-user@ws.apache.org Subject: wsdl2java behavior for multiple services in the same wsdl What is the expected behavior of the wsdl2java if there are multiple services defined in a wsdl file ? The option -sn allows you to choose a specific service when there are multiple multiple services in the wsdl. However, the help doesn't tell you what you are supposed to do if you want wsdl2java to generate code for *all* the services defined in the wsdl file. What I am seeing with the latest nightly build is that the wsdl2java generates code for *only* one of the services defined in the wsdl file (I didn't use -sn option). However the XmlBeans data binding classes are generated for all the services. Gul
