Re: Migrating to Axis 2
Time, people, other priorities...On 5/24/06, Scott McCoy <[EMAIL PROTECTED]> wrote: Unfortunately, that is unsatisfactory for migration.I wonder what is stopping there from being wrapping/unwrapping for the wrapped convention.- Scott On 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: No -- you just have to use a bean to wrap your parameters. AnneOn 5/20/06, Scott McCoy <[EMAIL PROTECTED]> wrote: I see, so I'm basically married to axis 1.3 for the time being. - ScottOn 5/20/06, Anne Thomas Manes < [EMAIL PROTECTED] > wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ... On 5/20/06, Scott McCoy < [EMAIL PROTECTED]> wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
Unfortunately, that is unsatisfactory for migration.I wonder what is stopping there from being wrapping/unwrapping for the wrapped convention.- ScottOn 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: No -- you just have to use a bean to wrap your parameters. AnneOn 5/20/06, Scott McCoy <[EMAIL PROTECTED]> wrote: I see, so I'm basically married to axis 1.3 for the time being. - ScottOn 5/20/06, Anne Thomas Manes < [EMAIL PROTECTED] > wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ... On 5/20/06, Scott McCoy < [EMAIL PROTECTED]> wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
No -- you just have to use a bean to wrap your parameters. AnneOn 5/20/06, Scott McCoy <[EMAIL PROTECTED]> wrote: I see, so I'm basically married to axis 1.3 for the time being. - ScottOn 5/20/06, Anne Thomas Manes < [EMAIL PROTECTED] > wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ... On 5/20/06, Scott McCoy < [EMAIL PROTECTED]> wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
I see, so I'm basically married to axis 1.3 for the time being.- ScottOn 5/20/06, Anne Thomas Manes <[EMAIL PROTECTED] > wrote:Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ... On 5/20/06, Scott McCoy < [EMAIL PROTECTED]> wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
Axis 2 does not yet support automatic unwrapping of wrapped doc/literal ...On 5/20/06, Scott McCoy <[EMAIL PROTECTED]> wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
" parameterOrder="i1 i2"> <wsdl:input message="impl:addRequest" name="addRequest" /> <wsdl:output message="impl:addResponse" name="addResponse" /> wsdl:operation> - <wsdl:operation name="subtract" parameterOrder="i1 i2"> <wsdl:input message="impl:subtractRequest" name="subtractRequest" /> <wsdl:output message="impl:subtractResponse" name="subtractResponse" /> wsdl:operation> wsdl:portType> - <wsdl:binding name="CalculatorSoapBinding" type="impl:Calculator"> <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" /> - <wsdl:operation name="add"> <wsdlsoap:operation soapAction="" /> - <wsdl:input name="addRequest"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://DefaultNamespace" use="encoded" /> wsdl:input> - <wsdl:output name="addResponse"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/axis/Calculator.jws" use="encoded" /> wsdl:output> wsdl:operation> - <wsdl:operation name="subtract"> <wsdlsoap:operation soapAction="" /> - <wsdl:input name="subtractRequest"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://DefaultNamespace" use="encoded" /> wsdl:input> - <wsdl:output name="subtractResponse"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/axis/Calculator.jws" use="encoded" /> wsdl:output> wsdl:operation> wsdl:binding> - <wsdl:service name="CalculatorService"> - <wsdl:port binding="impl:CalculatorSoapBinding" name="Calculator"> <wsdlsoap:address location="http://localhost:8080/axis/Calculator.jws" /> wsdl:port> wsdl:service> wsdl:definitions HTH, Martin -- This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you. - Original Message - From: robert lazarski To: axis-user@ws.apache.org Sent: Saturday, May 20, 2006 7:26 AM Subject: Re: Migrating to Axis 2 To help, I'd need to see your command line / ant options you are passing to wsdl2java. If you are migrating from axis 1.x , did you take a look at the databinding section in the migration guide? http://ws.apache.org/axis2/1_0/migration.htmlRoberthttp://www.braziloutsource.com/ On 5/20/06, Scott McCoy <[EMAIL PROTECTED] > wrote: Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy-To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating to Axis 2
To help, I'd need to see your command line / ant options you are passing to wsdl2java. If you are migrating from axis 1.x , did you take a look at the databinding section in the migration guide? http://ws.apache.org/axis2/1_0/migration.html Robert http://www.braziloutsource.com/On 5/20/06, Scott McCoy <[EMAIL PROTECTED] > wrote:Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java. Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Migrating to Axis 2
Okay, attached is a WSDL that worked fine for generating very simple to use wrapped document/literal services with WSDL2Java.Now, the code WSDL2Java generates is as though the wrapped document/literal convention is broken. It accepts a "Request" bean for each argument, and expects a "Response" bean in return.What the heck? Thanks, Scott S. McCoy http://plapi.enhance.com/service/account"; xmlns:tns="http://plapi.enhance.com/service/account"; xmlns:typens="http://plapi.enhance.com/service/account"; xmlns:authns="http://plapi.enhance.com/credentials"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> http://plapi.enhance.com/service/account";> http://schemas.xmlsoap.org/soap/http"/> http://plapi.enhance.com/services/AccountWebService"/> account.xsd Description: Binary data credentials.xsd Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
