You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by jackdawson <ab...@gmail.com> on 2008/09/26 16:15:30 UTC
Axis2 and CXF - Handling WSDLs differently
Here is what I found:
1.) When I used Axis2 Eclipse Codegen plugins (Generate Java source code
from WSDL file) to generate code from this WSDL, it didn't allow me.
It kept throwing me an error -
"An error occurred while completing the process -
java.lang.InterruptedException
No element type is defind for the message xxxxx"
2.) Then, I switched to CXF 2.0.8 and tried to generate the client as I did
with Axis2 and surprisingly, it got through and created the client side
stubs.
CXF doesn't see this WSDL as a bad one.
Please correct me if I'm wrong. To my knowledge, when you define "type"
attribute for the "message" and not the "element" attribute then it has to
be an "rpc" style.
Axis2 knows it but CXF ignores it.
Can anyone let me know why there's a difference in handling the WSDLs?
If I modify the WSDL as Axis2 wants me to and generate just the client and
hit the service (which is already existing), will I still be able to
succeed?
Here is the WSDL I'm talking about:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:login.safe.two.us"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="urn:login.safe.two.us"
xmlns:intf="urn:login.safe.two.us"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema elementFormDefault="qualified"
targetNamespace="urn:login.safe.two.us"
xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="TestLoginType">
<sequence>
<element name="eid" maxOccurs="1" minOccurs="1" type="xsd:string" />
<element name="key" nillable="true" type="xsd:string" />
</sequence>
</complexType>
<complexType name="TestLoginTypeResponse">
<sequence>
<element name="failedReason" nillable="true" type="xsd:string" />
<element name="status" type="xsd:boolean" />
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="testLoginRequest">
<wsdl:part name="testLoginRequestAttributes" type="impl:TestLoginType"/>
</wsdl:message>
<wsdl:message name="testLoginResponse">
<wsdl:part name="testLoginResponseAttributes"
type="impl:TestLoginTypeResponse"/>
</wsdl:message>
<wsdl:portType name="LoginServicePortType">
<wsdl:operation name="testLogin">
<wsdl:input message="impl:testLoginRequest" name="testLoginRequest" />
<wsdl:output message="impl:testLoginResponse" name="testLoginResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="LoginServiceSoapBinding"
type="impl:LoginServicePortType">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="testLogin">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="testLoginRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="testLoginResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="LoginService">
<wsdl:port binding="impl:LoginServiceSoapBinding" name="LoginService">
<wsdlsoap:address
location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks.
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
Thanks Keith. You are helpful and I kind of get your point.
I wonder how would I know whether the constraint is satisfied or not.
Is there any tutorial/documentum or any other resource that would help me in
fulfilling this?
I might really need a little push on this.
Thanks. I appreciate it.
Keithgchapman wrote:
>
> It depends. When RPC style is used the request should contain a wrapper
> element with the name of the operation. When document style is used it all
> depends o the schema that defines the elements (no magic elements). I
> wonder
> what your service really expects and editing the WSDL will have to make
> sure
> that this constrained is satisfied. I hope you get my point.
>
> Thanks,
> Keith.
>
> On Fri, Sep 26, 2008 at 8:05 PM, jackdawson <ab...@gmail.com>
> wrote:
>
>>
>> Thanks Keith. That's good to hear that Axis2 is more strict and reliable.
>>
>> Here is my dumb question now:
>> If I modify this WSDL and correct it and generate client stubs and access
>> the service, will I be able to succeed?
>>
>> Thanks.
>>
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > This WSDL looks invalid. As you have said when a message part refers
>> to
>> a
>> > type directly it is RPC whereas when it refers to an element its known
>> as
>> > document. Now the messages parts of your WSDL is RPC but your binsind
>> says
>> > that its document. I feel that the WSDL is incorrect and hence Axis2 is
>> > right in saying that the element is missing.
>> >
>> > Thanks,
>> > Keith.
>> >
>> > On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <ab...@gmail.com>
>> > wrote:
>> >
>> >>
>> >> Here is what I found:
>> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
>> >> source
>> >> code
>> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
>> >> It kept throwing me an error -
>> >> "An error occurred while completing the process
>> -
>> >> java.lang.InterruptedException
>> >> No element type is defind for the message
>> xxxxx"
>> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
>> client
>> >> as I did
>> >> with Axis2 and surprisingly, it got through and created the client
>> side
>> >> stubs.
>> >> CXF doesn't see this WSDL as a bad one.
>> >>
>> >> Please correct me if I'm wrong. To my knowledge, when
>> you
>> >> define "type"
>> >> attribute for the "message" and not the "element" attribute then it
>> has
>> >> to
>> >> be an "rpc" style.
>> >> Axis2 knows it but CXF ignores it.
>> >>
>> >> Can anyone let me know why there's a difference in
>> >> handling
>> >> the WSDLs?
>> >> If I modify the WSDL as Axis2 wants me to and generate
>> >> just
>> >> the client and
>> >> hit the service (which is already existing), will I still be able to
>> >> succeed?
>> >>
>> >> Here is the WSDL I'm talking about:
>> >>
>> >> <?xml version="1.0" encoding="UTF-8"?>
>> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us"
>> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> >> xmlns:impl="urn:login.safe.two.us"
>> >> xmlns:intf="urn:login.safe.two.us"
>> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> >> <wsdl:types>
>> >> <schema elementFormDefault="qualified"
>> >> targetNamespace="urn:login.safe.two.us"
>> >> xmlns="http://www.w3.org/2001/XMLSchema">
>> >>
>> >> <complexType name="TestLoginType">
>> >> <sequence>
>> >> <element name="eid"
>> maxOccurs="1"
>> >> minOccurs="1" type="xsd:string" />
>> >> <element name="key"
>> >> nillable="true"
>> >> type="xsd:string" />
>> >> </sequence>
>> >> </complexType>
>> >>
>> >> <complexType name="TestLoginTypeResponse">
>> >> <sequence>
>> >> <element name="failedReason"
>> >> nillable="true" type="xsd:string" />
>> >> <element name="status"
>> >> type="xsd:boolean" />
>> >> </sequence>
>> >> </complexType>
>> >>
>> >> </schema>
>> >> </wsdl:types>
>> >>
>> >> <wsdl:message name="testLoginRequest">
>> >> <wsdl:part name="testLoginRequestAttributes"
>> >> type="impl:TestLoginType"/>
>> >> </wsdl:message>
>> >>
>> >> <wsdl:message name="testLoginResponse">
>> >> <wsdl:part name="testLoginResponseAttributes"
>> >> type="impl:TestLoginTypeResponse"/>
>> >> </wsdl:message>
>> >>
>> >> <wsdl:portType name="LoginServicePortType">
>> >> <wsdl:operation name="testLogin">
>> >> <wsdl:input message="impl:testLoginRequest"
>> >> name="testLoginRequest" />
>> >> <wsdl:output message="impl:testLoginResponse"
>> >> name="testLoginResponse" />
>> >> </wsdl:operation>
>> >> </wsdl:portType>
>> >>
>> >> <wsdl:binding name="LoginServiceSoapBinding"
>> >> type="impl:LoginServicePortType">
>> >> <wsdlsoap:binding style="document"
>> >> transport="http://schemas.xmlsoap.org/soap/http" />
>> >> <wsdl:operation name="testLogin">
>> >> <wsdlsoap:operation soapAction="" />
>> >> <wsdl:input name="testLoginRequest">
>> >> <wsdlsoap:body use="literal" />
>> >> </wsdl:input>
>> >> <wsdl:output name="testLoginResponse">
>> >> <wsdlsoap:body use="literal" />
>> >> </wsdl:output>
>> >> </wsdl:operation>
>> >> </wsdl:binding>
>> >>
>> >> <wsdl:service name="LoginService">
>> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
>> >> name="LoginService">
>> >> <wsdlsoap:address
>> >>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> >> />
>> >> </wsdl:port>
>> >> </wsdl:service>
>> >> </wsdl:definitions>
>> >>
>> >>
>> >>
>> >> Thanks.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Keith Chapman
>> > Senior Software Engineer
>> > WSO2 Inc.
>> > Oxygenating the Web Service Platform.
>> > http://wso2.org/
>> >
>> > blog: http://www.keith-chapman.org
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689691.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19715170.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
It depends. When RPC style is used the request should contain a wrapper
element with the name of the operation. When document style is used it all
depends o the schema that defines the elements (no magic elements). I wonder
what your service really expects and editing the WSDL will have to make sure
that this constrained is satisfied. I hope you get my point.
Thanks,
Keith.
On Fri, Sep 26, 2008 at 8:05 PM, jackdawson <ab...@gmail.com> wrote:
>
> Thanks Keith. That's good to hear that Axis2 is more strict and reliable.
>
> Here is my dumb question now:
> If I modify this WSDL and correct it and generate client stubs and access
> the service, will I be able to succeed?
>
> Thanks.
>
>
>
>
> Keithgchapman wrote:
> >
> > This WSDL looks invalid. As you have said when a message part refers to
> a
> > type directly it is RPC whereas when it refers to an element its known as
> > document. Now the messages parts of your WSDL is RPC but your binsind
> says
> > that its document. I feel that the WSDL is incorrect and hence Axis2 is
> > right in saying that the element is missing.
> >
> > Thanks,
> > Keith.
> >
> > On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <ab...@gmail.com>
> > wrote:
> >
> >>
> >> Here is what I found:
> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> >> source
> >> code
> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
> >> It kept throwing me an error -
> >> "An error occurred while completing the process -
> >> java.lang.InterruptedException
> >> No element type is defind for the message xxxxx"
> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
> client
> >> as I did
> >> with Axis2 and surprisingly, it got through and created the client side
> >> stubs.
> >> CXF doesn't see this WSDL as a bad one.
> >>
> >> Please correct me if I'm wrong. To my knowledge, when you
> >> define "type"
> >> attribute for the "message" and not the "element" attribute then it has
> >> to
> >> be an "rpc" style.
> >> Axis2 knows it but CXF ignores it.
> >>
> >> Can anyone let me know why there's a difference in
> >> handling
> >> the WSDLs?
> >> If I modify the WSDL as Axis2 wants me to and generate
> >> just
> >> the client and
> >> hit the service (which is already existing), will I still be able to
> >> succeed?
> >>
> >> Here is the WSDL I'm talking about:
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us"
> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> xmlns:impl="urn:login.safe.two.us"
> >> xmlns:intf="urn:login.safe.two.us"
> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> <wsdl:types>
> >> <schema elementFormDefault="qualified"
> >> targetNamespace="urn:login.safe.two.us"
> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >>
> >> <complexType name="TestLoginType">
> >> <sequence>
> >> <element name="eid" maxOccurs="1"
> >> minOccurs="1" type="xsd:string" />
> >> <element name="key"
> >> nillable="true"
> >> type="xsd:string" />
> >> </sequence>
> >> </complexType>
> >>
> >> <complexType name="TestLoginTypeResponse">
> >> <sequence>
> >> <element name="failedReason"
> >> nillable="true" type="xsd:string" />
> >> <element name="status"
> >> type="xsd:boolean" />
> >> </sequence>
> >> </complexType>
> >>
> >> </schema>
> >> </wsdl:types>
> >>
> >> <wsdl:message name="testLoginRequest">
> >> <wsdl:part name="testLoginRequestAttributes"
> >> type="impl:TestLoginType"/>
> >> </wsdl:message>
> >>
> >> <wsdl:message name="testLoginResponse">
> >> <wsdl:part name="testLoginResponseAttributes"
> >> type="impl:TestLoginTypeResponse"/>
> >> </wsdl:message>
> >>
> >> <wsdl:portType name="LoginServicePortType">
> >> <wsdl:operation name="testLogin">
> >> <wsdl:input message="impl:testLoginRequest"
> >> name="testLoginRequest" />
> >> <wsdl:output message="impl:testLoginResponse"
> >> name="testLoginResponse" />
> >> </wsdl:operation>
> >> </wsdl:portType>
> >>
> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> type="impl:LoginServicePortType">
> >> <wsdlsoap:binding style="document"
> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> <wsdl:operation name="testLogin">
> >> <wsdlsoap:operation soapAction="" />
> >> <wsdl:input name="testLoginRequest">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:input>
> >> <wsdl:output name="testLoginResponse">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:output>
> >> </wsdl:operation>
> >> </wsdl:binding>
> >>
> >> <wsdl:service name="LoginService">
> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
> >> name="LoginService">
> >> <wsdlsoap:address
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> />
> >> </wsdl:port>
> >> </wsdl:service>
> >> </wsdl:definitions>
> >>
> >>
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689691.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
Thanks Keith. That's good to hear that Axis2 is more strict and reliable.
Here is my dumb question now:
If I modify this WSDL and correct it and generate client stubs and access
the service, will I be able to succeed?
Thanks.
Keithgchapman wrote:
>
> This WSDL looks invalid. As you have said when a message part refers to a
> type directly it is RPC whereas when it refers to an element its known as
> document. Now the messages parts of your WSDL is RPC but your binsind says
> that its document. I feel that the WSDL is incorrect and hence Axis2 is
> right in saying that the element is missing.
>
> Thanks,
> Keith.
>
> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <ab...@gmail.com>
> wrote:
>
>>
>> Here is what I found:
>> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
>> source
>> code
>> from WSDL file) to generate code from this WSDL, it didn't allow me.
>> It kept throwing me an error -
>> "An error occurred while completing the process -
>> java.lang.InterruptedException
>> No element type is defind for the message xxxxx"
>> 2.) Then, I switched to CXF 2.0.8 and tried to generate the client
>> as I did
>> with Axis2 and surprisingly, it got through and created the client side
>> stubs.
>> CXF doesn't see this WSDL as a bad one.
>>
>> Please correct me if I'm wrong. To my knowledge, when you
>> define "type"
>> attribute for the "message" and not the "element" attribute then it has
>> to
>> be an "rpc" style.
>> Axis2 knows it but CXF ignores it.
>>
>> Can anyone let me know why there's a difference in
>> handling
>> the WSDLs?
>> If I modify the WSDL as Axis2 wants me to and generate
>> just
>> the client and
>> hit the service (which is already existing), will I still be able to
>> succeed?
>>
>> Here is the WSDL I'm talking about:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <wsdl:definitions targetNamespace="urn:login.safe.two.us"
>> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> xmlns:impl="urn:login.safe.two.us"
>> xmlns:intf="urn:login.safe.two.us"
>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> <wsdl:types>
>> <schema elementFormDefault="qualified"
>> targetNamespace="urn:login.safe.two.us"
>> xmlns="http://www.w3.org/2001/XMLSchema">
>>
>> <complexType name="TestLoginType">
>> <sequence>
>> <element name="eid" maxOccurs="1"
>> minOccurs="1" type="xsd:string" />
>> <element name="key"
>> nillable="true"
>> type="xsd:string" />
>> </sequence>
>> </complexType>
>>
>> <complexType name="TestLoginTypeResponse">
>> <sequence>
>> <element name="failedReason"
>> nillable="true" type="xsd:string" />
>> <element name="status"
>> type="xsd:boolean" />
>> </sequence>
>> </complexType>
>>
>> </schema>
>> </wsdl:types>
>>
>> <wsdl:message name="testLoginRequest">
>> <wsdl:part name="testLoginRequestAttributes"
>> type="impl:TestLoginType"/>
>> </wsdl:message>
>>
>> <wsdl:message name="testLoginResponse">
>> <wsdl:part name="testLoginResponseAttributes"
>> type="impl:TestLoginTypeResponse"/>
>> </wsdl:message>
>>
>> <wsdl:portType name="LoginServicePortType">
>> <wsdl:operation name="testLogin">
>> <wsdl:input message="impl:testLoginRequest"
>> name="testLoginRequest" />
>> <wsdl:output message="impl:testLoginResponse"
>> name="testLoginResponse" />
>> </wsdl:operation>
>> </wsdl:portType>
>>
>> <wsdl:binding name="LoginServiceSoapBinding"
>> type="impl:LoginServicePortType">
>> <wsdlsoap:binding style="document"
>> transport="http://schemas.xmlsoap.org/soap/http" />
>> <wsdl:operation name="testLogin">
>> <wsdlsoap:operation soapAction="" />
>> <wsdl:input name="testLoginRequest">
>> <wsdlsoap:body use="literal" />
>> </wsdl:input>
>> <wsdl:output name="testLoginResponse">
>> <wsdlsoap:body use="literal" />
>> </wsdl:output>
>> </wsdl:operation>
>> </wsdl:binding>
>>
>> <wsdl:service name="LoginService">
>> <wsdl:port binding="impl:LoginServiceSoapBinding"
>> name="LoginService">
>> <wsdlsoap:address
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> />
>> </wsdl:port>
>> </wsdl:service>
>> </wsdl:definitions>
>>
>>
>>
>> Thanks.
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689691.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
Hmm, Now this is where the ambiguity of the WSDL comes into play. As it was
originally incorrect we are not sure what the payload should actually look,
Try adding another TestLoginType element around the SOAP body,
<soapenv:Body>
<q0:TestLoginType>
<q0:TestLoginType>
<q0:eid>ABC123</q0:eid>
<q0:key>KEY123</q0:key>
</q0:TestLoginType>
</q0:TestLoginType>
</soapenv:Body>
I'm not sure whether this would help but with an incorrect WSDL thats the
best you could do. Trial and error. (You should be able to modify this on
TCPMon and resend). BTW where did you get this WSDL from? (Just curios, was
it generated if so by what?).
Thanks,
Keith.
On Tue, Sep 30, 2008 at 4:28 AM, jackdawson <ab...@gmail.com> wrote:
>
> Yeah, I tried the one with Eclipse. I even changed the port to 9081 on
> which
> the TCP/IP Monitor listens but invain.
>
> I used the Web Services explorer and noted the SOAP messages, may be these
> would help:
>
> Request:
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:q0="urn:login.safe.two.us"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
> <q0:TestLoginType>
> <q0:eid>ABC123</q0:eid>
> <q0:key>KEY123</q0:key>
> </q0:TestLoginType>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Response:
> <soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:Client</faultcode>
> <faultstring>Parameter {urn:login.safe.two.us}TestLoginType
> does not
> exist!</faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
>
> Thanks.
>
>
>
>
>
>
> Keithgchapman wrote:
> >
> > TCPMon should wok irrespective of what your client or server is. It works
> > like a proxy sitting in between the client and server. Did you try to use
> > one of the plgins? Eclipse or Idea depending on what IDE you use.
> >
> > Thanks,
> > Keith.
> >
> > On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <ab...@gmail.com>
> > wrote:
> >
> >>
> >> If I'm not wrong then I get this when sending the request. This is the
> >> statement in the client that throws this exception:
> >>
> >> LoginServiceStub.TestLoginTypeResponse response =
> >>
> >> stub.testLogin(testLoginRequestAttributes);
> >>
> >> And, I don't know why but I can't get TCP Monitor get to work. I ran the
> >> client and it's hanging there in the console. I won't run and won't
> stop.
> >>
> >> Local Monitoring port: 8080
> >> Host name: JISLOGINDEV
> >> Port: 8080
> >> Type: HTTP
> >> Timeout: 0
> >>
> >> Dumb question again:
> >> My client is a simple Java app. Would TCP Monitor still work? I'm not
> >> running it on a server.
> >>
> >> Thanks.
> >>
> >>
> >>
> >> Keithgchapman wrote:
> >> >
> >> > Did you get this message while trying ti send the request or while
> >> > processing the response?
> >> >
> >> > You may use TCPMonitor as explained
> >> > here<
> >>
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >> >[1]
> >> > to capture the SOAP messages sent.
> >> >
> >> > Thanks,
> >> > Keith.
> >> >
> >> > [1]
> >> >
> >>
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >> >
> >> > On Mon, Sep 29, 2008 at 10:26 PM, jackdawson <ab...@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >> I changed the 'parts' to include element attributes and the WSDL is
> of
> >> >> 'document' style now. I generated the client stubs and the client and
> >> I'm
> >> >> still getting this exception:
> >> >>
> >> >> org.apache.axis2.AxisFault: Parameter
> >> >> {urn:login.safe.two.us}TestLoginType
> >> >> does not exist!
> >> >>
> >> >> I don't find where exactly it's going wrong even while debugging
> >> either.
> >> >> The service expects the parameters to be of type 'string' and that's
> >> what
> >> >> the client is sending.
> >> >>
> >> >> Here is the SOAP envelope:
> >> >>
> >> >> <?xml version='1.0' encoding='utf-8'?>
> >> >> <soapenv:Envelope
> >> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> >> >> ">
> >> >> <soapenv:Body>
> >> >> <ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
> >> >> <ns1:eid xmlns:s1="
> >> >> http://www.w3.org/2001/XMLSchema-instance"
> >> >>
> >> >> xmlns:s2="http://www.w3.org/2001/XMLSchema"
> >> >> s1:type="s2:string">G13522</ns1:eid>
> >> >> <ns1:key xmlns:s3="
> >> >> http://www.w3.org/2001/XMLSchema-instance"
> >> >>
> >> >> xmlns:s4="http://www.w3.org/2001/XMLSchema"
> >> >> s3:type="s4:string">P9534</ns1:key>
> >> >> </ns1:TestLoginType>
> >> >> </soapenv:Body>
> >> >> </soapenv:Envelope>
> >> >>
> >> >>
> >> >> Am I missing something here?
> >> >>
> >> >> Thanks.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Keithgchapman wrote:
> >> >> >
> >> >> > In your WSDL the parts section look RPC while the binding is
> >> document.
> >> >> I
> >> >> > recommend you that you make both of them the same. Either make both
> >> RPC
> >> >> > (just change the binding style to rpc) or both document (by making
> >> the
> >> >> > part
> >> >> > refer to an element instead of a type).
> >> >> >
> >> >> > Thanks,
> >> >> > Keith.
> >> >> >
> >> >> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <
> abhishek.foi@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> >>
> >> >> >> I posted in there too. They say that it's not mandatory to follow
> >> the
> >> >> >> WS-I
> >> >> >> basic profile as they are just guidelines and this is what they
> >> >> exactly
> >> >> >> said:
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >> >>
> >> >> >> Instead, I would like to get help in moving ahead with Axis2.
> >> >> >> Can anyone help me with this?
> >> >> >>
> >> >> >> Thanks.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> Sanjiva Weerawarana wrote:
> >> >> >> >
> >> >> >> > I can't imagine how CXF can generate code for this .. there's no
> >> >> >> element
> >> >> >> > name to use to put the data in. Maybe you should also post on
> >> >> >> > user@cxf.apache.org and ask for them to review this.
> >> >> >> >
> >> >> >> > Sanjiva.
> >> >> >> >
> >> >> >> > keith chapman wrote:
> >> >> >> >> This WSDL looks invalid. As you have said when a message part
> >> >> refers
> >> >> >> to
> >> >> >> >> a type directly it is RPC whereas when it refers to an element
> >> its
> >> >> >> known
> >> >> >> >> as document. Now the messages parts of your WSDL is RPC but
> your
> >> >> >> binsind
> >> >> >> >> says that its document. I feel that the WSDL is incorrect and
> >> hence
> >> >> >> >> Axis2 is right in saying that the element is missing.
> >> >> >> >>
> >> >> >> >> Thanks,
> >> >> >> >> Keith.
> >> >> >> >>
> >> >> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <
> >> abhishek.foi@gmail.com
> >> >> >> >> <ma...@gmail.com>> wrote:
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Here is what I found:
> >> >> >> >> 1.) When I used Axis2 Eclipse Codegen plugins
> >> (Generate
> >> >> >> Java
> >> >> >> >> source code
> >> >> >> >> from WSDL file) to generate code from this WSDL, it didn't
> >> >> allow
> >> >> >> me.
> >> >> >> >> It kept throwing me an error -
> >> >> >> >> "An error occurred while completing
> >> the
> >> >> >> >> process -
> >> >> >> >> java.lang.InterruptedException
> >> >> >> >> No element type is defind for the
> >> >> message
> >> >> >> >> xxxxx"
> >> >> >> >> 2.) Then, I switched to CXF 2.0.8 and tried to
> >> generate
> >> >> the
> >> >> >> >> client as I did
> >> >> >> >> with Axis2 and surprisingly, it got through and created the
> >> >> client
> >> >> >> >> side
> >> >> >> >> stubs.
> >> >> >> >> CXF doesn't see this WSDL as a bad one.
> >> >> >> >>
> >> >> >> >> Please correct me if I'm wrong. To my
> >> knowledge,
> >> >> >> when
> >> >> >> >> you define "type"
> >> >> >> >> attribute for the "message" and not the "element" attribute
> >> >> then
> >> >> >> it
> >> >> >> >> has to
> >> >> >> >> be an "rpc" style.
> >> >> >> >> Axis2 knows it but CXF ignores it.
> >> >> >> >>
> >> >> >> >> Can anyone let me know why there's a
> >> difference
> >> >> in
> >> >> >> >> handling the WSDLs?
> >> >> >> >> If I modify the WSDL as Axis2 wants me to
> and
> >> >> >> >> generate just the client and
> >> >> >> >> hit the service (which is already existing), will I still
> be
> >> >> able
> >> >> >> to
> >> >> >> >> succeed?
> >> >> >> >>
> >> >> >> >> Here is the WSDL I'm talking about:
> >> >> >> >>
> >> >> >> >> <?xml version="1.0" encoding="UTF-8"?>
> >> >> >> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> >> >> >> >> <http://login.safe.two.us>"
> >> >> >> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> >> >> >> xmlns:impl="urn:login.safe.two.us <
> >> >> http://login.safe.two.us
> >> >> >> >"
> >> >> >> >> xmlns:intf="urn:login.safe.two.us <
> >> >> http://login.safe.two.us
> >> >> >> >"
> >> >> >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> >> >> >>
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> >> >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> >> >> >> <wsdl:types>
> >> >> >> >> <schema elementFormDefault="qualified"
> >> >> >> >>
> >> targetNamespace="urn:login.safe.two.us
> >> >> >> >> <http://login.safe.two.us>"
> >> >> >> >>
> >> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >> >> >> >>
> >> >> >> >> <complexType name="TestLoginType">
> >> >> >> >> <sequence>
> >> >> >> >> <element name="eid"
> >> >> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> >> >> >> <element name="key"
> >> >> >> >> nillable="true" type="xsd:string" />
> >> >> >> >> </sequence>
> >> >> >> >> </complexType>
> >> >> >> >>
> >> >> >> >> <complexType
> >> >> name="TestLoginTypeResponse">
> >> >> >> >> <sequence>
> >> >> >> >> <element
> >> >> >> name="failedReason"
> >> >> >> >> nillable="true" type="xsd:string" />
> >> >> >> >> <element
> >> name="status"
> >> >> >> >> type="xsd:boolean" />
> >> >> >> >> </sequence>
> >> >> >> >> </complexType>
> >> >> >> >>
> >> >> >> >> </schema>
> >> >> >> >> </wsdl:types>
> >> >> >> >>
> >> >> >> >> <wsdl:message name="testLoginRequest">
> >> >> >> >> <wsdl:part name="testLoginRequestAttributes"
> >> >> >> >> type="impl:TestLoginType"/>
> >> >> >> >> </wsdl:message>
> >> >> >> >>
> >> >> >> >> <wsdl:message name="testLoginResponse">
> >> >> >> >> <wsdl:part
> name="testLoginResponseAttributes"
> >> >> >> >> type="impl:TestLoginTypeResponse"/>
> >> >> >> >> </wsdl:message>
> >> >> >> >>
> >> >> >> >> <wsdl:portType name="LoginServicePortType">
> >> >> >> >> <wsdl:operation name="testLogin">
> >> >> >> >> <wsdl:input
> >> >> message="impl:testLoginRequest"
> >> >> >> >> name="testLoginRequest" />
> >> >> >> >> <wsdl:output
> >> >> >> message="impl:testLoginResponse"
> >> >> >> >> name="testLoginResponse" />
> >> >> >> >> </wsdl:operation>
> >> >> >> >> </wsdl:portType>
> >> >> >> >>
> >> >> >> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> >> >> >> type="impl:LoginServicePortType">
> >> >> >> >> <wsdlsoap:binding style="document"
> >> >> >> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> >> >> >> <wsdl:operation name="testLogin">
> >> >> >> >> <wsdlsoap:operation soapAction="" />
> >> >> >> >> <wsdl:input name="testLoginRequest">
> >> >> >> >> <wsdlsoap:body use="literal"
> >> />
> >> >> >> >> </wsdl:input>
> >> >> >> >> <wsdl:output
> >> name="testLoginResponse">
> >> >> >> >> <wsdlsoap:body use="literal"
> >> />
> >> >> >> >> </wsdl:output>
> >> >> >> >> </wsdl:operation>
> >> >> >> >> </wsdl:binding>
> >> >> >> >>
> >> >> >> >> <wsdl:service name="LoginService">
> >> >> >> >> <wsdl:port
> >> >> binding="impl:LoginServiceSoapBinding"
> >> >> >> >> name="LoginService">
> >> >> >> >> <wsdlsoap:address
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> >> >> >> />
> >> >> >> >> </wsdl:port>
> >> >> >> >> </wsdl:service>
> >> >> >> >> </wsdl:definitions>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Thanks.
> >> >> >> >> --
> >> >> >> >> View this message in context:
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> >> >> >> Sent from the Axis - User mailing list archive at
> >> Nabble.com.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> ---------------------------------------------------------------------
> >> >> >> >> To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> >> >> >> >> <ma...@ws.apache.org>
> >> >> >> >> For additional commands, e-mail:
> >> axis-user-help@ws.apache.org
> >> >> >> >> <ma...@ws.apache.org>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Keith Chapman
> >> >> >> >> Senior Software Engineer
> >> >> >> >> WSO2 Inc.
> >> >> >> >> Oxygenating the Web Service Platform.
> >> >> >> >> http://wso2.org/
> >> >> >> >>
> >> >> >> >> blog: http://www.keith-chapman.org
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Sanjiva Weerawarana, Ph.D.
> >> >> >> > Founder & Director; Lanka Software Foundation;
> >> >> >> http://www.opensource.lk/
> >> >> >> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> >> >> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> >> >> > Visiting Lecturer; University of Moratuwa;
> >> http://www.cse.mrt.ac.lk/
> >> >> >> >
> >> >> >> > Blog: http://sanjiva.weerawarana.org/
> >> >> >> >
> >> >> >> >
> >> >> ---------------------------------------------------------------------
> >> >> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
> >> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Keith Chapman
> >> >> > Senior Software Engineer
> >> >> > WSO2 Inc.
> >> >> > Oxygenating the Web Service Platform.
> >> >> > http://wso2.org/
> >> >> >
> >> >> > blog: http://www.keith-chapman.org
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Keith Chapman
> >> > Senior Software Engineer
> >> > WSO2 Inc.
> >> > Oxygenating the Web Service Platform.
> >> > http://wso2.org/
> >> >
> >> > blog: http://www.keith-chapman.org
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19728636.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19733333.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
Yeah, I tried the one with Eclipse. I even changed the port to 9081 on which
the TCP/IP Monitor listens but invain.
I used the Web Services explorer and noted the SOAP messages, may be these
would help:
Request:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:q0="urn:login.safe.two.us"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<q0:TestLoginType>
<q0:eid>ABC123</q0:eid>
<q0:key>KEY123</q0:key>
</q0:TestLoginType>
</soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Parameter {urn:login.safe.two.us}TestLoginType does not
exist!</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Thanks.
Keithgchapman wrote:
>
> TCPMon should wok irrespective of what your client or server is. It works
> like a proxy sitting in between the client and server. Did you try to use
> one of the plgins? Eclipse or Idea depending on what IDE you use.
>
> Thanks,
> Keith.
>
> On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <ab...@gmail.com>
> wrote:
>
>>
>> If I'm not wrong then I get this when sending the request. This is the
>> statement in the client that throws this exception:
>>
>> LoginServiceStub.TestLoginTypeResponse response =
>>
>> stub.testLogin(testLoginRequestAttributes);
>>
>> And, I don't know why but I can't get TCP Monitor get to work. I ran the
>> client and it's hanging there in the console. I won't run and won't stop.
>>
>> Local Monitoring port: 8080
>> Host name: JISLOGINDEV
>> Port: 8080
>> Type: HTTP
>> Timeout: 0
>>
>> Dumb question again:
>> My client is a simple Java app. Would TCP Monitor still work? I'm not
>> running it on a server.
>>
>> Thanks.
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > Did you get this message while trying ti send the request or while
>> > processing the response?
>> >
>> > You may use TCPMonitor as explained
>> > here<
>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>> >[1]
>> > to capture the SOAP messages sent.
>> >
>> > Thanks,
>> > Keith.
>> >
>> > [1]
>> >
>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>> >
>> > On Mon, Sep 29, 2008 at 10:26 PM, jackdawson <ab...@gmail.com>
>> > wrote:
>> >
>> >>
>> >> I changed the 'parts' to include element attributes and the WSDL is of
>> >> 'document' style now. I generated the client stubs and the client and
>> I'm
>> >> still getting this exception:
>> >>
>> >> org.apache.axis2.AxisFault: Parameter
>> >> {urn:login.safe.two.us}TestLoginType
>> >> does not exist!
>> >>
>> >> I don't find where exactly it's going wrong even while debugging
>> either.
>> >> The service expects the parameters to be of type 'string' and that's
>> what
>> >> the client is sending.
>> >>
>> >> Here is the SOAP envelope:
>> >>
>> >> <?xml version='1.0' encoding='utf-8'?>
>> >> <soapenv:Envelope
>> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> >> ">
>> >> <soapenv:Body>
>> >> <ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
>> >> <ns1:eid xmlns:s1="
>> >> http://www.w3.org/2001/XMLSchema-instance"
>> >>
>> >> xmlns:s2="http://www.w3.org/2001/XMLSchema"
>> >> s1:type="s2:string">G13522</ns1:eid>
>> >> <ns1:key xmlns:s3="
>> >> http://www.w3.org/2001/XMLSchema-instance"
>> >>
>> >> xmlns:s4="http://www.w3.org/2001/XMLSchema"
>> >> s3:type="s4:string">P9534</ns1:key>
>> >> </ns1:TestLoginType>
>> >> </soapenv:Body>
>> >> </soapenv:Envelope>
>> >>
>> >>
>> >> Am I missing something here?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Keithgchapman wrote:
>> >> >
>> >> > In your WSDL the parts section look RPC while the binding is
>> document.
>> >> I
>> >> > recommend you that you make both of them the same. Either make both
>> RPC
>> >> > (just change the binding style to rpc) or both document (by making
>> the
>> >> > part
>> >> > refer to an element instead of a type).
>> >> >
>> >> > Thanks,
>> >> > Keith.
>> >> >
>> >> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com>
>> >> > wrote:
>> >> >
>> >> >>
>> >> >> I posted in there too. They say that it's not mandatory to follow
>> the
>> >> >> WS-I
>> >> >> basic profile as they are just guidelines and this is what they
>> >> exactly
>> >> >> said:
>> >> >>
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >> >>
>> >> >> Instead, I would like to get help in moving ahead with Axis2.
>> >> >> Can anyone help me with this?
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Sanjiva Weerawarana wrote:
>> >> >> >
>> >> >> > I can't imagine how CXF can generate code for this .. there's no
>> >> >> element
>> >> >> > name to use to put the data in. Maybe you should also post on
>> >> >> > user@cxf.apache.org and ask for them to review this.
>> >> >> >
>> >> >> > Sanjiva.
>> >> >> >
>> >> >> > keith chapman wrote:
>> >> >> >> This WSDL looks invalid. As you have said when a message part
>> >> refers
>> >> >> to
>> >> >> >> a type directly it is RPC whereas when it refers to an element
>> its
>> >> >> known
>> >> >> >> as document. Now the messages parts of your WSDL is RPC but your
>> >> >> binsind
>> >> >> >> says that its document. I feel that the WSDL is incorrect and
>> hence
>> >> >> >> Axis2 is right in saying that the element is missing.
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Keith.
>> >> >> >>
>> >> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <
>> abhishek.foi@gmail.com
>> >> >> >> <ma...@gmail.com>> wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> Here is what I found:
>> >> >> >> 1.) When I used Axis2 Eclipse Codegen plugins
>> (Generate
>> >> >> Java
>> >> >> >> source code
>> >> >> >> from WSDL file) to generate code from this WSDL, it didn't
>> >> allow
>> >> >> me.
>> >> >> >> It kept throwing me an error -
>> >> >> >> "An error occurred while completing
>> the
>> >> >> >> process -
>> >> >> >> java.lang.InterruptedException
>> >> >> >> No element type is defind for the
>> >> message
>> >> >> >> xxxxx"
>> >> >> >> 2.) Then, I switched to CXF 2.0.8 and tried to
>> generate
>> >> the
>> >> >> >> client as I did
>> >> >> >> with Axis2 and surprisingly, it got through and created the
>> >> client
>> >> >> >> side
>> >> >> >> stubs.
>> >> >> >> CXF doesn't see this WSDL as a bad one.
>> >> >> >>
>> >> >> >> Please correct me if I'm wrong. To my
>> knowledge,
>> >> >> when
>> >> >> >> you define "type"
>> >> >> >> attribute for the "message" and not the "element" attribute
>> >> then
>> >> >> it
>> >> >> >> has to
>> >> >> >> be an "rpc" style.
>> >> >> >> Axis2 knows it but CXF ignores it.
>> >> >> >>
>> >> >> >> Can anyone let me know why there's a
>> difference
>> >> in
>> >> >> >> handling the WSDLs?
>> >> >> >> If I modify the WSDL as Axis2 wants me to and
>> >> >> >> generate just the client and
>> >> >> >> hit the service (which is already existing), will I still be
>> >> able
>> >> >> to
>> >> >> >> succeed?
>> >> >> >>
>> >> >> >> Here is the WSDL I'm talking about:
>> >> >> >>
>> >> >> >> <?xml version="1.0" encoding="UTF-8"?>
>> >> >> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
>> >> >> >> <http://login.safe.two.us>"
>> >> >> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> >> >> >> xmlns:impl="urn:login.safe.two.us <
>> >> http://login.safe.two.us
>> >> >> >"
>> >> >> >> xmlns:intf="urn:login.safe.two.us <
>> >> http://login.safe.two.us
>> >> >> >"
>> >> >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> >> >> >>
>> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> >> >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> >> >> >> <wsdl:types>
>> >> >> >> <schema elementFormDefault="qualified"
>> >> >> >>
>> targetNamespace="urn:login.safe.two.us
>> >> >> >> <http://login.safe.two.us>"
>> >> >> >>
>> >> xmlns="http://www.w3.org/2001/XMLSchema">
>> >> >> >>
>> >> >> >> <complexType name="TestLoginType">
>> >> >> >> <sequence>
>> >> >> >> <element name="eid"
>> >> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
>> >> >> >> <element name="key"
>> >> >> >> nillable="true" type="xsd:string" />
>> >> >> >> </sequence>
>> >> >> >> </complexType>
>> >> >> >>
>> >> >> >> <complexType
>> >> name="TestLoginTypeResponse">
>> >> >> >> <sequence>
>> >> >> >> <element
>> >> >> name="failedReason"
>> >> >> >> nillable="true" type="xsd:string" />
>> >> >> >> <element
>> name="status"
>> >> >> >> type="xsd:boolean" />
>> >> >> >> </sequence>
>> >> >> >> </complexType>
>> >> >> >>
>> >> >> >> </schema>
>> >> >> >> </wsdl:types>
>> >> >> >>
>> >> >> >> <wsdl:message name="testLoginRequest">
>> >> >> >> <wsdl:part name="testLoginRequestAttributes"
>> >> >> >> type="impl:TestLoginType"/>
>> >> >> >> </wsdl:message>
>> >> >> >>
>> >> >> >> <wsdl:message name="testLoginResponse">
>> >> >> >> <wsdl:part name="testLoginResponseAttributes"
>> >> >> >> type="impl:TestLoginTypeResponse"/>
>> >> >> >> </wsdl:message>
>> >> >> >>
>> >> >> >> <wsdl:portType name="LoginServicePortType">
>> >> >> >> <wsdl:operation name="testLogin">
>> >> >> >> <wsdl:input
>> >> message="impl:testLoginRequest"
>> >> >> >> name="testLoginRequest" />
>> >> >> >> <wsdl:output
>> >> >> message="impl:testLoginResponse"
>> >> >> >> name="testLoginResponse" />
>> >> >> >> </wsdl:operation>
>> >> >> >> </wsdl:portType>
>> >> >> >>
>> >> >> >> <wsdl:binding name="LoginServiceSoapBinding"
>> >> >> >> type="impl:LoginServicePortType">
>> >> >> >> <wsdlsoap:binding style="document"
>> >> >> >> transport="http://schemas.xmlsoap.org/soap/http" />
>> >> >> >> <wsdl:operation name="testLogin">
>> >> >> >> <wsdlsoap:operation soapAction="" />
>> >> >> >> <wsdl:input name="testLoginRequest">
>> >> >> >> <wsdlsoap:body use="literal"
>> />
>> >> >> >> </wsdl:input>
>> >> >> >> <wsdl:output
>> name="testLoginResponse">
>> >> >> >> <wsdlsoap:body use="literal"
>> />
>> >> >> >> </wsdl:output>
>> >> >> >> </wsdl:operation>
>> >> >> >> </wsdl:binding>
>> >> >> >>
>> >> >> >> <wsdl:service name="LoginService">
>> >> >> >> <wsdl:port
>> >> binding="impl:LoginServiceSoapBinding"
>> >> >> >> name="LoginService">
>> >> >> >> <wsdlsoap:address
>> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> >> >> >> />
>> >> >> >> </wsdl:port>
>> >> >> >> </wsdl:service>
>> >> >> >> </wsdl:definitions>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Thanks.
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> >> >> >> Sent from the Axis - User mailing list archive at
>> Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >> >> <ma...@ws.apache.org>
>> >> >> >> For additional commands, e-mail:
>> axis-user-help@ws.apache.org
>> >> >> >> <ma...@ws.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Keith Chapman
>> >> >> >> Senior Software Engineer
>> >> >> >> WSO2 Inc.
>> >> >> >> Oxygenating the Web Service Platform.
>> >> >> >> http://wso2.org/
>> >> >> >>
>> >> >> >> blog: http://www.keith-chapman.org
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Sanjiva Weerawarana, Ph.D.
>> >> >> > Founder & Director; Lanka Software Foundation;
>> >> >> http://www.opensource.lk/
>> >> >> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> >> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> >> > Visiting Lecturer; University of Moratuwa;
>> http://www.cse.mrt.ac.lk/
>> >> >> >
>> >> >> > Blog: http://sanjiva.weerawarana.org/
>> >> >> >
>> >> >> >
>> >> ---------------------------------------------------------------------
>> >> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
>> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Keith Chapman
>> >> > Senior Software Engineer
>> >> > WSO2 Inc.
>> >> > Oxygenating the Web Service Platform.
>> >> > http://wso2.org/
>> >> >
>> >> > blog: http://www.keith-chapman.org
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Keith Chapman
>> > Senior Software Engineer
>> > WSO2 Inc.
>> > Oxygenating the Web Service Platform.
>> > http://wso2.org/
>> >
>> > blog: http://www.keith-chapman.org
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19728636.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19733333.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
TCPMon should wok irrespective of what your client or server is. It works
like a proxy sitting in between the client and server. Did you try to use
one of the plgins? Eclipse or Idea depending on what IDE you use.
Thanks,
Keith.
On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <ab...@gmail.com> wrote:
>
> If I'm not wrong then I get this when sending the request. This is the
> statement in the client that throws this exception:
>
> LoginServiceStub.TestLoginTypeResponse response =
>
> stub.testLogin(testLoginRequestAttributes);
>
> And, I don't know why but I can't get TCP Monitor get to work. I ran the
> client and it's hanging there in the console. I won't run and won't stop.
>
> Local Monitoring port: 8080
> Host name: JISLOGINDEV
> Port: 8080
> Type: HTTP
> Timeout: 0
>
> Dumb question again:
> My client is a simple Java app. Would TCP Monitor still work? I'm not
> running it on a server.
>
> Thanks.
>
>
>
> Keithgchapman wrote:
> >
> > Did you get this message while trying ti send the request or while
> > processing the response?
> >
> > You may use TCPMonitor as explained
> > here<
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >[1]
> > to capture the SOAP messages sent.
> >
> > Thanks,
> > Keith.
> >
> > [1]
> >
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >
> > On Mon, Sep 29, 2008 at 10:26 PM, jackdawson <ab...@gmail.com>
> > wrote:
> >
> >>
> >> I changed the 'parts' to include element attributes and the WSDL is of
> >> 'document' style now. I generated the client stubs and the client and
> I'm
> >> still getting this exception:
> >>
> >> org.apache.axis2.AxisFault: Parameter
> >> {urn:login.safe.two.us}TestLoginType
> >> does not exist!
> >>
> >> I don't find where exactly it's going wrong even while debugging either.
> >> The service expects the parameters to be of type 'string' and that's
> what
> >> the client is sending.
> >>
> >> Here is the SOAP envelope:
> >>
> >> <?xml version='1.0' encoding='utf-8'?>
> >> <soapenv:Envelope
> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> >> ">
> >> <soapenv:Body>
> >> <ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
> >> <ns1:eid xmlns:s1="
> >> http://www.w3.org/2001/XMLSchema-instance"
> >>
> >> xmlns:s2="http://www.w3.org/2001/XMLSchema"
> >> s1:type="s2:string">G13522</ns1:eid>
> >> <ns1:key xmlns:s3="
> >> http://www.w3.org/2001/XMLSchema-instance"
> >>
> >> xmlns:s4="http://www.w3.org/2001/XMLSchema"
> >> s3:type="s4:string">P9534</ns1:key>
> >> </ns1:TestLoginType>
> >> </soapenv:Body>
> >> </soapenv:Envelope>
> >>
> >>
> >> Am I missing something here?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Keithgchapman wrote:
> >> >
> >> > In your WSDL the parts section look RPC while the binding is document.
> >> I
> >> > recommend you that you make both of them the same. Either make both
> RPC
> >> > (just change the binding style to rpc) or both document (by making the
> >> > part
> >> > refer to an element instead of a type).
> >> >
> >> > Thanks,
> >> > Keith.
> >> >
> >> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >> I posted in there too. They say that it's not mandatory to follow the
> >> >> WS-I
> >> >> basic profile as they are just guidelines and this is what they
> >> exactly
> >> >> said:
> >> >>
> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >>
> >> >> Instead, I would like to get help in moving ahead with Axis2.
> >> >> Can anyone help me with this?
> >> >>
> >> >> Thanks.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Sanjiva Weerawarana wrote:
> >> >> >
> >> >> > I can't imagine how CXF can generate code for this .. there's no
> >> >> element
> >> >> > name to use to put the data in. Maybe you should also post on
> >> >> > user@cxf.apache.org and ask for them to review this.
> >> >> >
> >> >> > Sanjiva.
> >> >> >
> >> >> > keith chapman wrote:
> >> >> >> This WSDL looks invalid. As you have said when a message part
> >> refers
> >> >> to
> >> >> >> a type directly it is RPC whereas when it refers to an element its
> >> >> known
> >> >> >> as document. Now the messages parts of your WSDL is RPC but your
> >> >> binsind
> >> >> >> says that its document. I feel that the WSDL is incorrect and
> hence
> >> >> >> Axis2 is right in saying that the element is missing.
> >> >> >>
> >> >> >> Thanks,
> >> >> >> Keith.
> >> >> >>
> >> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <
> abhishek.foi@gmail.com
> >> >> >> <ma...@gmail.com>> wrote:
> >> >> >>
> >> >> >>
> >> >> >> Here is what I found:
> >> >> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate
> >> >> Java
> >> >> >> source code
> >> >> >> from WSDL file) to generate code from this WSDL, it didn't
> >> allow
> >> >> me.
> >> >> >> It kept throwing me an error -
> >> >> >> "An error occurred while completing the
> >> >> >> process -
> >> >> >> java.lang.InterruptedException
> >> >> >> No element type is defind for the
> >> message
> >> >> >> xxxxx"
> >> >> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate
> >> the
> >> >> >> client as I did
> >> >> >> with Axis2 and surprisingly, it got through and created the
> >> client
> >> >> >> side
> >> >> >> stubs.
> >> >> >> CXF doesn't see this WSDL as a bad one.
> >> >> >>
> >> >> >> Please correct me if I'm wrong. To my
> knowledge,
> >> >> when
> >> >> >> you define "type"
> >> >> >> attribute for the "message" and not the "element" attribute
> >> then
> >> >> it
> >> >> >> has to
> >> >> >> be an "rpc" style.
> >> >> >> Axis2 knows it but CXF ignores it.
> >> >> >>
> >> >> >> Can anyone let me know why there's a difference
> >> in
> >> >> >> handling the WSDLs?
> >> >> >> If I modify the WSDL as Axis2 wants me to and
> >> >> >> generate just the client and
> >> >> >> hit the service (which is already existing), will I still be
> >> able
> >> >> to
> >> >> >> succeed?
> >> >> >>
> >> >> >> Here is the WSDL I'm talking about:
> >> >> >>
> >> >> >> <?xml version="1.0" encoding="UTF-8"?>
> >> >> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> >> >> >> <http://login.safe.two.us>"
> >> >> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> >> >> xmlns:impl="urn:login.safe.two.us <
> >> http://login.safe.two.us
> >> >> >"
> >> >> >> xmlns:intf="urn:login.safe.two.us <
> >> http://login.safe.two.us
> >> >> >"
> >> >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> >> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> >> >> <wsdl:types>
> >> >> >> <schema elementFormDefault="qualified"
> >> >> >> targetNamespace="urn:login.safe.two.us
> >> >> >> <http://login.safe.two.us>"
> >> >> >>
> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >> >> >>
> >> >> >> <complexType name="TestLoginType">
> >> >> >> <sequence>
> >> >> >> <element name="eid"
> >> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> >> >> <element name="key"
> >> >> >> nillable="true" type="xsd:string" />
> >> >> >> </sequence>
> >> >> >> </complexType>
> >> >> >>
> >> >> >> <complexType
> >> name="TestLoginTypeResponse">
> >> >> >> <sequence>
> >> >> >> <element
> >> >> name="failedReason"
> >> >> >> nillable="true" type="xsd:string" />
> >> >> >> <element name="status"
> >> >> >> type="xsd:boolean" />
> >> >> >> </sequence>
> >> >> >> </complexType>
> >> >> >>
> >> >> >> </schema>
> >> >> >> </wsdl:types>
> >> >> >>
> >> >> >> <wsdl:message name="testLoginRequest">
> >> >> >> <wsdl:part name="testLoginRequestAttributes"
> >> >> >> type="impl:TestLoginType"/>
> >> >> >> </wsdl:message>
> >> >> >>
> >> >> >> <wsdl:message name="testLoginResponse">
> >> >> >> <wsdl:part name="testLoginResponseAttributes"
> >> >> >> type="impl:TestLoginTypeResponse"/>
> >> >> >> </wsdl:message>
> >> >> >>
> >> >> >> <wsdl:portType name="LoginServicePortType">
> >> >> >> <wsdl:operation name="testLogin">
> >> >> >> <wsdl:input
> >> message="impl:testLoginRequest"
> >> >> >> name="testLoginRequest" />
> >> >> >> <wsdl:output
> >> >> message="impl:testLoginResponse"
> >> >> >> name="testLoginResponse" />
> >> >> >> </wsdl:operation>
> >> >> >> </wsdl:portType>
> >> >> >>
> >> >> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> >> >> type="impl:LoginServicePortType">
> >> >> >> <wsdlsoap:binding style="document"
> >> >> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> >> >> <wsdl:operation name="testLogin">
> >> >> >> <wsdlsoap:operation soapAction="" />
> >> >> >> <wsdl:input name="testLoginRequest">
> >> >> >> <wsdlsoap:body use="literal" />
> >> >> >> </wsdl:input>
> >> >> >> <wsdl:output name="testLoginResponse">
> >> >> >> <wsdlsoap:body use="literal" />
> >> >> >> </wsdl:output>
> >> >> >> </wsdl:operation>
> >> >> >> </wsdl:binding>
> >> >> >>
> >> >> >> <wsdl:service name="LoginService">
> >> >> >> <wsdl:port
> >> binding="impl:LoginServiceSoapBinding"
> >> >> >> name="LoginService">
> >> >> >> <wsdlsoap:address
> >> >> >>
> >> >> >>
> >> >>
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> >> >> />
> >> >> >> </wsdl:port>
> >> >> >> </wsdl:service>
> >> >> >> </wsdl:definitions>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> Thanks.
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> >> <ma...@ws.apache.org>
> >> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >> <ma...@ws.apache.org>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Keith Chapman
> >> >> >> Senior Software Engineer
> >> >> >> WSO2 Inc.
> >> >> >> Oxygenating the Web Service Platform.
> >> >> >> http://wso2.org/
> >> >> >>
> >> >> >> blog: http://www.keith-chapman.org
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Sanjiva Weerawarana, Ph.D.
> >> >> > Founder & Director; Lanka Software Foundation;
> >> >> http://www.opensource.lk/
> >> >> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> >> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> >> > Visiting Lecturer; University of Moratuwa;
> http://www.cse.mrt.ac.lk/
> >> >> >
> >> >> > Blog: http://sanjiva.weerawarana.org/
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Keith Chapman
> >> > Senior Software Engineer
> >> > WSO2 Inc.
> >> > Oxygenating the Web Service Platform.
> >> > http://wso2.org/
> >> >
> >> > blog: http://www.keith-chapman.org
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19728636.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
If I'm not wrong then I get this when sending the request. This is the
statement in the client that throws this exception:
LoginServiceStub.TestLoginTypeResponse response =
stub.testLogin(testLoginRequestAttributes);
And, I don't know why but I can't get TCP Monitor get to work. I ran the
client and it's hanging there in the console. I won't run and won't stop.
Local Monitoring port: 8080
Host name: JISLOGINDEV
Port: 8080
Type: HTTP
Timeout: 0
Dumb question again:
My client is a simple Java app. Would TCP Monitor still work? I'm not
running it on a server.
Thanks.
Keithgchapman wrote:
>
> Did you get this message while trying ti send the request or while
> processing the response?
>
> You may use TCPMonitor as explained
> here<http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html>[1]
> to capture the SOAP messages sent.
>
> Thanks,
> Keith.
>
> [1]
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>
> On Mon, Sep 29, 2008 at 10:26 PM, jackdawson <ab...@gmail.com>
> wrote:
>
>>
>> I changed the 'parts' to include element attributes and the WSDL is of
>> 'document' style now. I generated the client stubs and the client and I'm
>> still getting this exception:
>>
>> org.apache.axis2.AxisFault: Parameter
>> {urn:login.safe.two.us}TestLoginType
>> does not exist!
>>
>> I don't find where exactly it's going wrong even while debugging either.
>> The service expects the parameters to be of type 'string' and that's what
>> the client is sending.
>>
>> Here is the SOAP envelope:
>>
>> <?xml version='1.0' encoding='utf-8'?>
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> ">
>> <soapenv:Body>
>> <ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
>> <ns1:eid xmlns:s1="
>> http://www.w3.org/2001/XMLSchema-instance"
>>
>> xmlns:s2="http://www.w3.org/2001/XMLSchema"
>> s1:type="s2:string">G13522</ns1:eid>
>> <ns1:key xmlns:s3="
>> http://www.w3.org/2001/XMLSchema-instance"
>>
>> xmlns:s4="http://www.w3.org/2001/XMLSchema"
>> s3:type="s4:string">P9534</ns1:key>
>> </ns1:TestLoginType>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>>
>> Am I missing something here?
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > In your WSDL the parts section look RPC while the binding is document.
>> I
>> > recommend you that you make both of them the same. Either make both RPC
>> > (just change the binding style to rpc) or both document (by making the
>> > part
>> > refer to an element instead of a type).
>> >
>> > Thanks,
>> > Keith.
>> >
>> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com>
>> > wrote:
>> >
>> >>
>> >> I posted in there too. They say that it's not mandatory to follow the
>> >> WS-I
>> >> basic profile as they are just guidelines and this is what they
>> exactly
>> >> said:
>> >>
>> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >>
>> >> Instead, I would like to get help in moving ahead with Axis2.
>> >> Can anyone help me with this?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >> Sanjiva Weerawarana wrote:
>> >> >
>> >> > I can't imagine how CXF can generate code for this .. there's no
>> >> element
>> >> > name to use to put the data in. Maybe you should also post on
>> >> > user@cxf.apache.org and ask for them to review this.
>> >> >
>> >> > Sanjiva.
>> >> >
>> >> > keith chapman wrote:
>> >> >> This WSDL looks invalid. As you have said when a message part
>> refers
>> >> to
>> >> >> a type directly it is RPC whereas when it refers to an element its
>> >> known
>> >> >> as document. Now the messages parts of your WSDL is RPC but your
>> >> binsind
>> >> >> says that its document. I feel that the WSDL is incorrect and hence
>> >> >> Axis2 is right in saying that the element is missing.
>> >> >>
>> >> >> Thanks,
>> >> >> Keith.
>> >> >>
>> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
>> >> >> <ma...@gmail.com>> wrote:
>> >> >>
>> >> >>
>> >> >> Here is what I found:
>> >> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate
>> >> Java
>> >> >> source code
>> >> >> from WSDL file) to generate code from this WSDL, it didn't
>> allow
>> >> me.
>> >> >> It kept throwing me an error -
>> >> >> "An error occurred while completing the
>> >> >> process -
>> >> >> java.lang.InterruptedException
>> >> >> No element type is defind for the
>> message
>> >> >> xxxxx"
>> >> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate
>> the
>> >> >> client as I did
>> >> >> with Axis2 and surprisingly, it got through and created the
>> client
>> >> >> side
>> >> >> stubs.
>> >> >> CXF doesn't see this WSDL as a bad one.
>> >> >>
>> >> >> Please correct me if I'm wrong. To my knowledge,
>> >> when
>> >> >> you define "type"
>> >> >> attribute for the "message" and not the "element" attribute
>> then
>> >> it
>> >> >> has to
>> >> >> be an "rpc" style.
>> >> >> Axis2 knows it but CXF ignores it.
>> >> >>
>> >> >> Can anyone let me know why there's a difference
>> in
>> >> >> handling the WSDLs?
>> >> >> If I modify the WSDL as Axis2 wants me to and
>> >> >> generate just the client and
>> >> >> hit the service (which is already existing), will I still be
>> able
>> >> to
>> >> >> succeed?
>> >> >>
>> >> >> Here is the WSDL I'm talking about:
>> >> >>
>> >> >> <?xml version="1.0" encoding="UTF-8"?>
>> >> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
>> >> >> <http://login.safe.two.us>"
>> >> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> >> >> xmlns:impl="urn:login.safe.two.us <
>> http://login.safe.two.us
>> >> >"
>> >> >> xmlns:intf="urn:login.safe.two.us <
>> http://login.safe.two.us
>> >> >"
>> >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> >> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> >> >> <wsdl:types>
>> >> >> <schema elementFormDefault="qualified"
>> >> >> targetNamespace="urn:login.safe.two.us
>> >> >> <http://login.safe.two.us>"
>> >> >>
>> xmlns="http://www.w3.org/2001/XMLSchema">
>> >> >>
>> >> >> <complexType name="TestLoginType">
>> >> >> <sequence>
>> >> >> <element name="eid"
>> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
>> >> >> <element name="key"
>> >> >> nillable="true" type="xsd:string" />
>> >> >> </sequence>
>> >> >> </complexType>
>> >> >>
>> >> >> <complexType
>> name="TestLoginTypeResponse">
>> >> >> <sequence>
>> >> >> <element
>> >> name="failedReason"
>> >> >> nillable="true" type="xsd:string" />
>> >> >> <element name="status"
>> >> >> type="xsd:boolean" />
>> >> >> </sequence>
>> >> >> </complexType>
>> >> >>
>> >> >> </schema>
>> >> >> </wsdl:types>
>> >> >>
>> >> >> <wsdl:message name="testLoginRequest">
>> >> >> <wsdl:part name="testLoginRequestAttributes"
>> >> >> type="impl:TestLoginType"/>
>> >> >> </wsdl:message>
>> >> >>
>> >> >> <wsdl:message name="testLoginResponse">
>> >> >> <wsdl:part name="testLoginResponseAttributes"
>> >> >> type="impl:TestLoginTypeResponse"/>
>> >> >> </wsdl:message>
>> >> >>
>> >> >> <wsdl:portType name="LoginServicePortType">
>> >> >> <wsdl:operation name="testLogin">
>> >> >> <wsdl:input
>> message="impl:testLoginRequest"
>> >> >> name="testLoginRequest" />
>> >> >> <wsdl:output
>> >> message="impl:testLoginResponse"
>> >> >> name="testLoginResponse" />
>> >> >> </wsdl:operation>
>> >> >> </wsdl:portType>
>> >> >>
>> >> >> <wsdl:binding name="LoginServiceSoapBinding"
>> >> >> type="impl:LoginServicePortType">
>> >> >> <wsdlsoap:binding style="document"
>> >> >> transport="http://schemas.xmlsoap.org/soap/http" />
>> >> >> <wsdl:operation name="testLogin">
>> >> >> <wsdlsoap:operation soapAction="" />
>> >> >> <wsdl:input name="testLoginRequest">
>> >> >> <wsdlsoap:body use="literal" />
>> >> >> </wsdl:input>
>> >> >> <wsdl:output name="testLoginResponse">
>> >> >> <wsdlsoap:body use="literal" />
>> >> >> </wsdl:output>
>> >> >> </wsdl:operation>
>> >> >> </wsdl:binding>
>> >> >>
>> >> >> <wsdl:service name="LoginService">
>> >> >> <wsdl:port
>> binding="impl:LoginServiceSoapBinding"
>> >> >> name="LoginService">
>> >> >> <wsdlsoap:address
>> >> >>
>> >> >>
>> >>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> >> >> />
>> >> >> </wsdl:port>
>> >> >> </wsdl:service>
>> >> >> </wsdl:definitions>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thanks.
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >> <ma...@ws.apache.org>
>> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >> <ma...@ws.apache.org>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Keith Chapman
>> >> >> Senior Software Engineer
>> >> >> WSO2 Inc.
>> >> >> Oxygenating the Web Service Platform.
>> >> >> http://wso2.org/
>> >> >>
>> >> >> blog: http://www.keith-chapman.org
>> >> >
>> >> >
>> >> > --
>> >> > Sanjiva Weerawarana, Ph.D.
>> >> > Founder & Director; Lanka Software Foundation;
>> >> http://www.opensource.lk/
>> >> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>> >> >
>> >> > Blog: http://sanjiva.weerawarana.org/
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Keith Chapman
>> > Senior Software Engineer
>> > WSO2 Inc.
>> > Oxygenating the Web Service Platform.
>> > http://wso2.org/
>> >
>> > blog: http://www.keith-chapman.org
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19728636.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
Did you get this message while trying ti send the request or while
processing the response?
You may use TCPMonitor as explained
here<http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html>[1]
to capture the SOAP messages sent.
Thanks,
Keith.
[1]
http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
On Mon, Sep 29, 2008 at 10:26 PM, jackdawson <ab...@gmail.com> wrote:
>
> I changed the 'parts' to include element attributes and the WSDL is of
> 'document' style now. I generated the client stubs and the client and I'm
> still getting this exception:
>
> org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
> does not exist!
>
> I don't find where exactly it's going wrong even while debugging either.
> The service expects the parameters to be of type 'string' and that's what
> the client is sending.
>
> Here is the SOAP envelope:
>
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> ">
> <soapenv:Body>
> <ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
> <ns1:eid xmlns:s1="
> http://www.w3.org/2001/XMLSchema-instance"
> xmlns:s2="http://www.w3.org/2001/XMLSchema"
> s1:type="s2:string">G13522</ns1:eid>
> <ns1:key xmlns:s3="
> http://www.w3.org/2001/XMLSchema-instance"
> xmlns:s4="http://www.w3.org/2001/XMLSchema"
> s3:type="s4:string">P9534</ns1:key>
> </ns1:TestLoginType>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Am I missing something here?
>
> Thanks.
>
>
>
>
>
>
>
>
>
> Keithgchapman wrote:
> >
> > In your WSDL the parts section look RPC while the binding is document. I
> > recommend you that you make both of them the same. Either make both RPC
> > (just change the binding style to rpc) or both document (by making the
> > part
> > refer to an element instead of a type).
> >
> > Thanks,
> > Keith.
> >
> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com>
> > wrote:
> >
> >>
> >> I posted in there too. They say that it's not mandatory to follow the
> >> WS-I
> >> basic profile as they are just guidelines and this is what they exactly
> >> said:
> >>
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >>
> >> Instead, I would like to get help in moving ahead with Axis2.
> >> Can anyone help me with this?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >> Sanjiva Weerawarana wrote:
> >> >
> >> > I can't imagine how CXF can generate code for this .. there's no
> >> element
> >> > name to use to put the data in. Maybe you should also post on
> >> > user@cxf.apache.org and ask for them to review this.
> >> >
> >> > Sanjiva.
> >> >
> >> > keith chapman wrote:
> >> >> This WSDL looks invalid. As you have said when a message part refers
> >> to
> >> >> a type directly it is RPC whereas when it refers to an element its
> >> known
> >> >> as document. Now the messages parts of your WSDL is RPC but your
> >> binsind
> >> >> says that its document. I feel that the WSDL is incorrect and hence
> >> >> Axis2 is right in saying that the element is missing.
> >> >>
> >> >> Thanks,
> >> >> Keith.
> >> >>
> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
> >> >> <ma...@gmail.com>> wrote:
> >> >>
> >> >>
> >> >> Here is what I found:
> >> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate
> >> Java
> >> >> source code
> >> >> from WSDL file) to generate code from this WSDL, it didn't allow
> >> me.
> >> >> It kept throwing me an error -
> >> >> "An error occurred while completing the
> >> >> process -
> >> >> java.lang.InterruptedException
> >> >> No element type is defind for the message
> >> >> xxxxx"
> >> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate
> the
> >> >> client as I did
> >> >> with Axis2 and surprisingly, it got through and created the
> client
> >> >> side
> >> >> stubs.
> >> >> CXF doesn't see this WSDL as a bad one.
> >> >>
> >> >> Please correct me if I'm wrong. To my knowledge,
> >> when
> >> >> you define "type"
> >> >> attribute for the "message" and not the "element" attribute then
> >> it
> >> >> has to
> >> >> be an "rpc" style.
> >> >> Axis2 knows it but CXF ignores it.
> >> >>
> >> >> Can anyone let me know why there's a difference in
> >> >> handling the WSDLs?
> >> >> If I modify the WSDL as Axis2 wants me to and
> >> >> generate just the client and
> >> >> hit the service (which is already existing), will I still be able
> >> to
> >> >> succeed?
> >> >>
> >> >> Here is the WSDL I'm talking about:
> >> >>
> >> >> <?xml version="1.0" encoding="UTF-8"?>
> >> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> >> >> <http://login.safe.two.us>"
> >> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> >> xmlns:impl="urn:login.safe.two.us <
> http://login.safe.two.us
> >> >"
> >> >> xmlns:intf="urn:login.safe.two.us <
> http://login.safe.two.us
> >> >"
> >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> >> <wsdl:types>
> >> >> <schema elementFormDefault="qualified"
> >> >> targetNamespace="urn:login.safe.two.us
> >> >> <http://login.safe.two.us>"
> >> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >> >>
> >> >> <complexType name="TestLoginType">
> >> >> <sequence>
> >> >> <element name="eid"
> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> >> <element name="key"
> >> >> nillable="true" type="xsd:string" />
> >> >> </sequence>
> >> >> </complexType>
> >> >>
> >> >> <complexType name="TestLoginTypeResponse">
> >> >> <sequence>
> >> >> <element
> >> name="failedReason"
> >> >> nillable="true" type="xsd:string" />
> >> >> <element name="status"
> >> >> type="xsd:boolean" />
> >> >> </sequence>
> >> >> </complexType>
> >> >>
> >> >> </schema>
> >> >> </wsdl:types>
> >> >>
> >> >> <wsdl:message name="testLoginRequest">
> >> >> <wsdl:part name="testLoginRequestAttributes"
> >> >> type="impl:TestLoginType"/>
> >> >> </wsdl:message>
> >> >>
> >> >> <wsdl:message name="testLoginResponse">
> >> >> <wsdl:part name="testLoginResponseAttributes"
> >> >> type="impl:TestLoginTypeResponse"/>
> >> >> </wsdl:message>
> >> >>
> >> >> <wsdl:portType name="LoginServicePortType">
> >> >> <wsdl:operation name="testLogin">
> >> >> <wsdl:input
> message="impl:testLoginRequest"
> >> >> name="testLoginRequest" />
> >> >> <wsdl:output
> >> message="impl:testLoginResponse"
> >> >> name="testLoginResponse" />
> >> >> </wsdl:operation>
> >> >> </wsdl:portType>
> >> >>
> >> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> >> type="impl:LoginServicePortType">
> >> >> <wsdlsoap:binding style="document"
> >> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> >> <wsdl:operation name="testLogin">
> >> >> <wsdlsoap:operation soapAction="" />
> >> >> <wsdl:input name="testLoginRequest">
> >> >> <wsdlsoap:body use="literal" />
> >> >> </wsdl:input>
> >> >> <wsdl:output name="testLoginResponse">
> >> >> <wsdlsoap:body use="literal" />
> >> >> </wsdl:output>
> >> >> </wsdl:operation>
> >> >> </wsdl:binding>
> >> >>
> >> >> <wsdl:service name="LoginService">
> >> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
> >> >> name="LoginService">
> >> >> <wsdlsoap:address
> >> >>
> >> >>
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> >> />
> >> >> </wsdl:port>
> >> >> </wsdl:service>
> >> >> </wsdl:definitions>
> >> >>
> >> >>
> >> >>
> >> >> Thanks.
> >> >> --
> >> >> View this message in context:
> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >>
> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> <ma...@ws.apache.org>
> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> <ma...@ws.apache.org>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Keith Chapman
> >> >> Senior Software Engineer
> >> >> WSO2 Inc.
> >> >> Oxygenating the Web Service Platform.
> >> >> http://wso2.org/
> >> >>
> >> >> blog: http://www.keith-chapman.org
> >> >
> >> >
> >> > --
> >> > Sanjiva Weerawarana, Ph.D.
> >> > Founder & Director; Lanka Software Foundation;
> >> http://www.opensource.lk/
> >> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> >> >
> >> > Blog: http://sanjiva.weerawarana.org/
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
I changed the 'parts' to include element attributes and the WSDL is of
'document' style now. I generated the client stubs and the client and I'm
still getting this exception:
org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
does not exist!
I don't find where exactly it's going wrong even while debugging either.
The service expects the parameters to be of type 'string' and that's what
the client is sending.
Here is the SOAP envelope:
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:TestLoginType xmlns:ns1="urn:login.safe.two.us">
<ns1:eid xmlns:s1="http://www.w3.org/2001/XMLSchema-instance"
xmlns:s2="http://www.w3.org/2001/XMLSchema"
s1:type="s2:string">G13522</ns1:eid>
<ns1:key xmlns:s3="http://www.w3.org/2001/XMLSchema-instance"
xmlns:s4="http://www.w3.org/2001/XMLSchema"
s3:type="s4:string">P9534</ns1:key>
</ns1:TestLoginType>
</soapenv:Body>
</soapenv:Envelope>
Am I missing something here?
Thanks.
Keithgchapman wrote:
>
> In your WSDL the parts section look RPC while the binding is document. I
> recommend you that you make both of them the same. Either make both RPC
> (just change the binding style to rpc) or both document (by making the
> part
> refer to an element instead of a type).
>
> Thanks,
> Keith.
>
> On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com>
> wrote:
>
>>
>> I posted in there too. They say that it's not mandatory to follow the
>> WS-I
>> basic profile as they are just guidelines and this is what they exactly
>> said:
>>
>>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>>
>> Instead, I would like to get help in moving ahead with Axis2.
>> Can anyone help me with this?
>>
>> Thanks.
>>
>>
>>
>>
>> Sanjiva Weerawarana wrote:
>> >
>> > I can't imagine how CXF can generate code for this .. there's no
>> element
>> > name to use to put the data in. Maybe you should also post on
>> > user@cxf.apache.org and ask for them to review this.
>> >
>> > Sanjiva.
>> >
>> > keith chapman wrote:
>> >> This WSDL looks invalid. As you have said when a message part refers
>> to
>> >> a type directly it is RPC whereas when it refers to an element its
>> known
>> >> as document. Now the messages parts of your WSDL is RPC but your
>> binsind
>> >> says that its document. I feel that the WSDL is incorrect and hence
>> >> Axis2 is right in saying that the element is missing.
>> >>
>> >> Thanks,
>> >> Keith.
>> >>
>> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
>> >> <ma...@gmail.com>> wrote:
>> >>
>> >>
>> >> Here is what I found:
>> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate
>> Java
>> >> source code
>> >> from WSDL file) to generate code from this WSDL, it didn't allow
>> me.
>> >> It kept throwing me an error -
>> >> "An error occurred while completing the
>> >> process -
>> >> java.lang.InterruptedException
>> >> No element type is defind for the message
>> >> xxxxx"
>> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
>> >> client as I did
>> >> with Axis2 and surprisingly, it got through and created the client
>> >> side
>> >> stubs.
>> >> CXF doesn't see this WSDL as a bad one.
>> >>
>> >> Please correct me if I'm wrong. To my knowledge,
>> when
>> >> you define "type"
>> >> attribute for the "message" and not the "element" attribute then
>> it
>> >> has to
>> >> be an "rpc" style.
>> >> Axis2 knows it but CXF ignores it.
>> >>
>> >> Can anyone let me know why there's a difference in
>> >> handling the WSDLs?
>> >> If I modify the WSDL as Axis2 wants me to and
>> >> generate just the client and
>> >> hit the service (which is already existing), will I still be able
>> to
>> >> succeed?
>> >>
>> >> Here is the WSDL I'm talking about:
>> >>
>> >> <?xml version="1.0" encoding="UTF-8"?>
>> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
>> >> <http://login.safe.two.us>"
>> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> >> xmlns:impl="urn:login.safe.two.us <http://login.safe.two.us
>> >"
>> >> xmlns:intf="urn:login.safe.two.us <http://login.safe.two.us
>> >"
>> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> >> <wsdl:types>
>> >> <schema elementFormDefault="qualified"
>> >> targetNamespace="urn:login.safe.two.us
>> >> <http://login.safe.two.us>"
>> >> xmlns="http://www.w3.org/2001/XMLSchema">
>> >>
>> >> <complexType name="TestLoginType">
>> >> <sequence>
>> >> <element name="eid"
>> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
>> >> <element name="key"
>> >> nillable="true" type="xsd:string" />
>> >> </sequence>
>> >> </complexType>
>> >>
>> >> <complexType name="TestLoginTypeResponse">
>> >> <sequence>
>> >> <element
>> name="failedReason"
>> >> nillable="true" type="xsd:string" />
>> >> <element name="status"
>> >> type="xsd:boolean" />
>> >> </sequence>
>> >> </complexType>
>> >>
>> >> </schema>
>> >> </wsdl:types>
>> >>
>> >> <wsdl:message name="testLoginRequest">
>> >> <wsdl:part name="testLoginRequestAttributes"
>> >> type="impl:TestLoginType"/>
>> >> </wsdl:message>
>> >>
>> >> <wsdl:message name="testLoginResponse">
>> >> <wsdl:part name="testLoginResponseAttributes"
>> >> type="impl:TestLoginTypeResponse"/>
>> >> </wsdl:message>
>> >>
>> >> <wsdl:portType name="LoginServicePortType">
>> >> <wsdl:operation name="testLogin">
>> >> <wsdl:input message="impl:testLoginRequest"
>> >> name="testLoginRequest" />
>> >> <wsdl:output
>> message="impl:testLoginResponse"
>> >> name="testLoginResponse" />
>> >> </wsdl:operation>
>> >> </wsdl:portType>
>> >>
>> >> <wsdl:binding name="LoginServiceSoapBinding"
>> >> type="impl:LoginServicePortType">
>> >> <wsdlsoap:binding style="document"
>> >> transport="http://schemas.xmlsoap.org/soap/http" />
>> >> <wsdl:operation name="testLogin">
>> >> <wsdlsoap:operation soapAction="" />
>> >> <wsdl:input name="testLoginRequest">
>> >> <wsdlsoap:body use="literal" />
>> >> </wsdl:input>
>> >> <wsdl:output name="testLoginResponse">
>> >> <wsdlsoap:body use="literal" />
>> >> </wsdl:output>
>> >> </wsdl:operation>
>> >> </wsdl:binding>
>> >>
>> >> <wsdl:service name="LoginService">
>> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
>> >> name="LoginService">
>> >> <wsdlsoap:address
>> >>
>> >>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> >> />
>> >> </wsdl:port>
>> >> </wsdl:service>
>> >> </wsdl:definitions>
>> >>
>> >>
>> >>
>> >> Thanks.
>> >> --
>> >> View this message in context:
>> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> <ma...@ws.apache.org>
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> <ma...@ws.apache.org>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Keith Chapman
>> >> Senior Software Engineer
>> >> WSO2 Inc.
>> >> Oxygenating the Web Service Platform.
>> >> http://wso2.org/
>> >>
>> >> blog: http://www.keith-chapman.org
>> >
>> >
>> > --
>> > Sanjiva Weerawarana, Ph.D.
>> > Founder & Director; Lanka Software Foundation;
>> http://www.opensource.lk/
>> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>> >
>> > Blog: http://sanjiva.weerawarana.org/
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19727637.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
In your WSDL the parts section look RPC while the binding is document. I
recommend you that you make both of them the same. Either make both RPC
(just change the binding style to rpc) or both document (by making the part
refer to an element instead of a type).
Thanks,
Keith.
On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com> wrote:
>
> I posted in there too. They say that it's not mandatory to follow the WS-I
> basic profile as they are just guidelines and this is what they exactly
> said:
>
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> Instead, I would like to get help in moving ahead with Axis2.
> Can anyone help me with this?
>
> Thanks.
>
>
>
>
> Sanjiva Weerawarana wrote:
> >
> > I can't imagine how CXF can generate code for this .. there's no element
> > name to use to put the data in. Maybe you should also post on
> > user@cxf.apache.org and ask for them to review this.
> >
> > Sanjiva.
> >
> > keith chapman wrote:
> >> This WSDL looks invalid. As you have said when a message part refers to
> >> a type directly it is RPC whereas when it refers to an element its known
> >> as document. Now the messages parts of your WSDL is RPC but your binsind
> >> says that its document. I feel that the WSDL is incorrect and hence
> >> Axis2 is right in saying that the element is missing.
> >>
> >> Thanks,
> >> Keith.
> >>
> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
> >> <ma...@gmail.com>> wrote:
> >>
> >>
> >> Here is what I found:
> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> >> source code
> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
> >> It kept throwing me an error -
> >> "An error occurred while completing the
> >> process -
> >> java.lang.InterruptedException
> >> No element type is defind for the message
> >> xxxxx"
> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
> >> client as I did
> >> with Axis2 and surprisingly, it got through and created the client
> >> side
> >> stubs.
> >> CXF doesn't see this WSDL as a bad one.
> >>
> >> Please correct me if I'm wrong. To my knowledge, when
> >> you define "type"
> >> attribute for the "message" and not the "element" attribute then it
> >> has to
> >> be an "rpc" style.
> >> Axis2 knows it but CXF ignores it.
> >>
> >> Can anyone let me know why there's a difference in
> >> handling the WSDLs?
> >> If I modify the WSDL as Axis2 wants me to and
> >> generate just the client and
> >> hit the service (which is already existing), will I still be able to
> >> succeed?
> >>
> >> Here is the WSDL I'm talking about:
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> >> <http://login.safe.two.us>"
> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> xmlns:impl="urn:login.safe.two.us <http://login.safe.two.us
> >"
> >> xmlns:intf="urn:login.safe.two.us <http://login.safe.two.us
> >"
> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> <wsdl:types>
> >> <schema elementFormDefault="qualified"
> >> targetNamespace="urn:login.safe.two.us
> >> <http://login.safe.two.us>"
> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >>
> >> <complexType name="TestLoginType">
> >> <sequence>
> >> <element name="eid"
> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> <element name="key"
> >> nillable="true" type="xsd:string" />
> >> </sequence>
> >> </complexType>
> >>
> >> <complexType name="TestLoginTypeResponse">
> >> <sequence>
> >> <element name="failedReason"
> >> nillable="true" type="xsd:string" />
> >> <element name="status"
> >> type="xsd:boolean" />
> >> </sequence>
> >> </complexType>
> >>
> >> </schema>
> >> </wsdl:types>
> >>
> >> <wsdl:message name="testLoginRequest">
> >> <wsdl:part name="testLoginRequestAttributes"
> >> type="impl:TestLoginType"/>
> >> </wsdl:message>
> >>
> >> <wsdl:message name="testLoginResponse">
> >> <wsdl:part name="testLoginResponseAttributes"
> >> type="impl:TestLoginTypeResponse"/>
> >> </wsdl:message>
> >>
> >> <wsdl:portType name="LoginServicePortType">
> >> <wsdl:operation name="testLogin">
> >> <wsdl:input message="impl:testLoginRequest"
> >> name="testLoginRequest" />
> >> <wsdl:output message="impl:testLoginResponse"
> >> name="testLoginResponse" />
> >> </wsdl:operation>
> >> </wsdl:portType>
> >>
> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> type="impl:LoginServicePortType">
> >> <wsdlsoap:binding style="document"
> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> <wsdl:operation name="testLogin">
> >> <wsdlsoap:operation soapAction="" />
> >> <wsdl:input name="testLoginRequest">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:input>
> >> <wsdl:output name="testLoginResponse">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:output>
> >> </wsdl:operation>
> >> </wsdl:binding>
> >>
> >> <wsdl:service name="LoginService">
> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
> >> name="LoginService">
> >> <wsdlsoap:address
> >>
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> />
> >> </wsdl:port>
> >> </wsdl:service>
> >> </wsdl:definitions>
> >>
> >>
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> <ma...@ws.apache.org>
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> <ma...@ws.apache.org>
> >>
> >>
> >>
> >>
> >> --
> >> Keith Chapman
> >> Senior Software Engineer
> >> WSO2 Inc.
> >> Oxygenating the Web Service Platform.
> >> http://wso2.org/
> >>
> >> blog: http://www.keith-chapman.org
> >
> >
> > --
> > Sanjiva Weerawarana, Ph.D.
> > Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> > Member; Apache Software Foundation; http://www.apache.org/
> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> >
> > Blog: http://sanjiva.weerawarana.org/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <ab...@gmail.com> wrote:
>
> I posted in there too. They say that it's not mandatory to follow the WS-I
> basic profile as they are just guidelines and this is what they exactly
> said:
>
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
Interesting replies on the CXF list. Its true that its not required for a
WSDL to be WS-I compliant to be valid. But irrespective of what WS-I says I
think this WSDL is invalid (According to the WSDL spec). Section 3.4 [1] of
the WSDL spec states that "The *style* attribute indicates whether the
operation is RPC-oriented (messages containing parameters and return values)
or document-oriented (message containing document(s))." It clearly states
there that referring to types from a part is RPC and referring to elements
from a part is document style.
I don't see how its possible for parts to be RPC and the binding to be
document. This sure could be confusing and this is the very reason why WSDL
2.0 got rid of this mess. In WSDL 2.0 everything is doc/lit.
Thanks,
Keith.
[1] http://www.w3.org/TR/wsdl#_soap:operation
>
> <http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html>
>
> Instead, I would like to get help in moving ahead with Axis2.
> Can anyone help me with this?
>
> Thanks.
>
>
>
>
> Sanjiva Weerawarana wrote:
> >
> > I can't imagine how CXF can generate code for this .. there's no element
> > name to use to put the data in. Maybe you should also post on
> > user@cxf.apache.org and ask for them to review this.
> >
> > Sanjiva.
> >
> > keith chapman wrote:
> >> This WSDL looks invalid. As you have said when a message part refers to
> >> a type directly it is RPC whereas when it refers to an element its known
> >> as document. Now the messages parts of your WSDL is RPC but your binsind
> >> says that its document. I feel that the WSDL is incorrect and hence
> >> Axis2 is right in saying that the element is missing.
> >>
> >> Thanks,
> >> Keith.
> >>
> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
> >> <ma...@gmail.com>> wrote:
> >>
> >>
> >> Here is what I found:
> >> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> >> source code
> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
> >> It kept throwing me an error -
> >> "An error occurred while completing the
> >> process -
> >> java.lang.InterruptedException
> >> No element type is defind for the message
> >> xxxxx"
> >> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
> >> client as I did
> >> with Axis2 and surprisingly, it got through and created the client
> >> side
> >> stubs.
> >> CXF doesn't see this WSDL as a bad one.
> >>
> >> Please correct me if I'm wrong. To my knowledge, when
> >> you define "type"
> >> attribute for the "message" and not the "element" attribute then it
> >> has to
> >> be an "rpc" style.
> >> Axis2 knows it but CXF ignores it.
> >>
> >> Can anyone let me know why there's a difference in
> >> handling the WSDLs?
> >> If I modify the WSDL as Axis2 wants me to and
> >> generate just the client and
> >> hit the service (which is already existing), will I still be able to
> >> succeed?
> >>
> >> Here is the WSDL I'm talking about:
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> >> <http://login.safe.two.us>"
> >> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >> xmlns:impl="urn:login.safe.two.us <http://login.safe.two.us
> >"
> >> xmlns:intf="urn:login.safe.two.us <http://login.safe.two.us
> >"
> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >> <wsdl:types>
> >> <schema elementFormDefault="qualified"
> >> targetNamespace="urn:login.safe.two.us
> >> <http://login.safe.two.us>"
> >> xmlns="http://www.w3.org/2001/XMLSchema">
> >>
> >> <complexType name="TestLoginType">
> >> <sequence>
> >> <element name="eid"
> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> <element name="key"
> >> nillable="true" type="xsd:string" />
> >> </sequence>
> >> </complexType>
> >>
> >> <complexType name="TestLoginTypeResponse">
> >> <sequence>
> >> <element name="failedReason"
> >> nillable="true" type="xsd:string" />
> >> <element name="status"
> >> type="xsd:boolean" />
> >> </sequence>
> >> </complexType>
> >>
> >> </schema>
> >> </wsdl:types>
> >>
> >> <wsdl:message name="testLoginRequest">
> >> <wsdl:part name="testLoginRequestAttributes"
> >> type="impl:TestLoginType"/>
> >> </wsdl:message>
> >>
> >> <wsdl:message name="testLoginResponse">
> >> <wsdl:part name="testLoginResponseAttributes"
> >> type="impl:TestLoginTypeResponse"/>
> >> </wsdl:message>
> >>
> >> <wsdl:portType name="LoginServicePortType">
> >> <wsdl:operation name="testLogin">
> >> <wsdl:input message="impl:testLoginRequest"
> >> name="testLoginRequest" />
> >> <wsdl:output message="impl:testLoginResponse"
> >> name="testLoginResponse" />
> >> </wsdl:operation>
> >> </wsdl:portType>
> >>
> >> <wsdl:binding name="LoginServiceSoapBinding"
> >> type="impl:LoginServicePortType">
> >> <wsdlsoap:binding style="document"
> >> transport="http://schemas.xmlsoap.org/soap/http" />
> >> <wsdl:operation name="testLogin">
> >> <wsdlsoap:operation soapAction="" />
> >> <wsdl:input name="testLoginRequest">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:input>
> >> <wsdl:output name="testLoginResponse">
> >> <wsdlsoap:body use="literal" />
> >> </wsdl:output>
> >> </wsdl:operation>
> >> </wsdl:binding>
> >>
> >> <wsdl:service name="LoginService">
> >> <wsdl:port binding="impl:LoginServiceSoapBinding"
> >> name="LoginService">
> >> <wsdlsoap:address
> >>
> >> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> >> />
> >> </wsdl:port>
> >> </wsdl:service>
> >> </wsdl:definitions>
> >>
> >>
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> <ma...@ws.apache.org>
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> <ma...@ws.apache.org>
> >>
> >>
> >>
> >>
> >> --
> >> Keith Chapman
> >> Senior Software Engineer
> >> WSO2 Inc.
> >> Oxygenating the Web Service Platform.
> >> http://wso2.org/
> >>
> >> blog: http://www.keith-chapman.org
> >
> >
> > --
> > Sanjiva Weerawarana, Ph.D.
> > Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> > Member; Apache Software Foundation; http://www.apache.org/
> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> >
> > Blog: http://sanjiva.weerawarana.org/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by jackdawson <ab...@gmail.com>.
I posted in there too. They say that it's not mandatory to follow the WS-I
basic profile as they are just guidelines and this is what they exactly
said:
http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
Instead, I would like to get help in moving ahead with Axis2.
Can anyone help me with this?
Thanks.
Sanjiva Weerawarana wrote:
>
> I can't imagine how CXF can generate code for this .. there's no element
> name to use to put the data in. Maybe you should also post on
> user@cxf.apache.org and ask for them to review this.
>
> Sanjiva.
>
> keith chapman wrote:
>> This WSDL looks invalid. As you have said when a message part refers to
>> a type directly it is RPC whereas when it refers to an element its known
>> as document. Now the messages parts of your WSDL is RPC but your binsind
>> says that its document. I feel that the WSDL is incorrect and hence
>> Axis2 is right in saying that the element is missing.
>>
>> Thanks,
>> Keith.
>>
>> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>>
>> Here is what I found:
>> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
>> source code
>> from WSDL file) to generate code from this WSDL, it didn't allow me.
>> It kept throwing me an error -
>> "An error occurred while completing the
>> process -
>> java.lang.InterruptedException
>> No element type is defind for the message
>> xxxxx"
>> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
>> client as I did
>> with Axis2 and surprisingly, it got through and created the client
>> side
>> stubs.
>> CXF doesn't see this WSDL as a bad one.
>>
>> Please correct me if I'm wrong. To my knowledge, when
>> you define "type"
>> attribute for the "message" and not the "element" attribute then it
>> has to
>> be an "rpc" style.
>> Axis2 knows it but CXF ignores it.
>>
>> Can anyone let me know why there's a difference in
>> handling the WSDLs?
>> If I modify the WSDL as Axis2 wants me to and
>> generate just the client and
>> hit the service (which is already existing), will I still be able to
>> succeed?
>>
>> Here is the WSDL I'm talking about:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <wsdl:definitions targetNamespace="urn:login.safe.two.us
>> <http://login.safe.two.us>"
>> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> xmlns:impl="urn:login.safe.two.us <http://login.safe.two.us>"
>> xmlns:intf="urn:login.safe.two.us <http://login.safe.two.us>"
>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> <wsdl:types>
>> <schema elementFormDefault="qualified"
>> targetNamespace="urn:login.safe.two.us
>> <http://login.safe.two.us>"
>> xmlns="http://www.w3.org/2001/XMLSchema">
>>
>> <complexType name="TestLoginType">
>> <sequence>
>> <element name="eid"
>> maxOccurs="1" minOccurs="1" type="xsd:string" />
>> <element name="key"
>> nillable="true" type="xsd:string" />
>> </sequence>
>> </complexType>
>>
>> <complexType name="TestLoginTypeResponse">
>> <sequence>
>> <element name="failedReason"
>> nillable="true" type="xsd:string" />
>> <element name="status"
>> type="xsd:boolean" />
>> </sequence>
>> </complexType>
>>
>> </schema>
>> </wsdl:types>
>>
>> <wsdl:message name="testLoginRequest">
>> <wsdl:part name="testLoginRequestAttributes"
>> type="impl:TestLoginType"/>
>> </wsdl:message>
>>
>> <wsdl:message name="testLoginResponse">
>> <wsdl:part name="testLoginResponseAttributes"
>> type="impl:TestLoginTypeResponse"/>
>> </wsdl:message>
>>
>> <wsdl:portType name="LoginServicePortType">
>> <wsdl:operation name="testLogin">
>> <wsdl:input message="impl:testLoginRequest"
>> name="testLoginRequest" />
>> <wsdl:output message="impl:testLoginResponse"
>> name="testLoginResponse" />
>> </wsdl:operation>
>> </wsdl:portType>
>>
>> <wsdl:binding name="LoginServiceSoapBinding"
>> type="impl:LoginServicePortType">
>> <wsdlsoap:binding style="document"
>> transport="http://schemas.xmlsoap.org/soap/http" />
>> <wsdl:operation name="testLogin">
>> <wsdlsoap:operation soapAction="" />
>> <wsdl:input name="testLoginRequest">
>> <wsdlsoap:body use="literal" />
>> </wsdl:input>
>> <wsdl:output name="testLoginResponse">
>> <wsdlsoap:body use="literal" />
>> </wsdl:output>
>> </wsdl:operation>
>> </wsdl:binding>
>>
>> <wsdl:service name="LoginService">
>> <wsdl:port binding="impl:LoginServiceSoapBinding"
>> name="LoginService">
>> <wsdlsoap:address
>>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
>> />
>> </wsdl:port>
>> </wsdl:service>
>> </wsdl:definitions>
>>
>>
>>
>> Thanks.
>> --
>> View this message in context:
>>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19723842.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I can't imagine how CXF can generate code for this .. there's no element
name to use to put the data in. Maybe you should also post on
user@cxf.apache.org and ask for them to review this.
Sanjiva.
keith chapman wrote:
> This WSDL looks invalid. As you have said when a message part refers to
> a type directly it is RPC whereas when it refers to an element its known
> as document. Now the messages parts of your WSDL is RPC but your binsind
> says that its document. I feel that the WSDL is incorrect and hence
> Axis2 is right in saying that the element is missing.
>
> Thanks,
> Keith.
>
> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <abhishek.foi@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> Here is what I found:
> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> source code
> from WSDL file) to generate code from this WSDL, it didn't allow me.
> It kept throwing me an error -
> "An error occurred while completing the process -
> java.lang.InterruptedException
> No element type is defind for the message xxxxx"
> 2.) Then, I switched to CXF 2.0.8 and tried to generate the
> client as I did
> with Axis2 and surprisingly, it got through and created the client side
> stubs.
> CXF doesn't see this WSDL as a bad one.
>
> Please correct me if I'm wrong. To my knowledge, when
> you define "type"
> attribute for the "message" and not the "element" attribute then it
> has to
> be an "rpc" style.
> Axis2 knows it but CXF ignores it.
>
> Can anyone let me know why there's a difference in
> handling the WSDLs?
> If I modify the WSDL as Axis2 wants me to and
> generate just the client and
> hit the service (which is already existing), will I still be able to
> succeed?
>
> Here is the WSDL I'm talking about:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions targetNamespace="urn:login.safe.two.us
> <http://login.safe.two.us>"
> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> xmlns:impl="urn:login.safe.two.us <http://login.safe.two.us>"
> xmlns:intf="urn:login.safe.two.us <http://login.safe.two.us>"
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <wsdl:types>
> <schema elementFormDefault="qualified"
> targetNamespace="urn:login.safe.two.us
> <http://login.safe.two.us>"
> xmlns="http://www.w3.org/2001/XMLSchema">
>
> <complexType name="TestLoginType">
> <sequence>
> <element name="eid"
> maxOccurs="1" minOccurs="1" type="xsd:string" />
> <element name="key"
> nillable="true" type="xsd:string" />
> </sequence>
> </complexType>
>
> <complexType name="TestLoginTypeResponse">
> <sequence>
> <element name="failedReason"
> nillable="true" type="xsd:string" />
> <element name="status"
> type="xsd:boolean" />
> </sequence>
> </complexType>
>
> </schema>
> </wsdl:types>
>
> <wsdl:message name="testLoginRequest">
> <wsdl:part name="testLoginRequestAttributes"
> type="impl:TestLoginType"/>
> </wsdl:message>
>
> <wsdl:message name="testLoginResponse">
> <wsdl:part name="testLoginResponseAttributes"
> type="impl:TestLoginTypeResponse"/>
> </wsdl:message>
>
> <wsdl:portType name="LoginServicePortType">
> <wsdl:operation name="testLogin">
> <wsdl:input message="impl:testLoginRequest"
> name="testLoginRequest" />
> <wsdl:output message="impl:testLoginResponse"
> name="testLoginResponse" />
> </wsdl:operation>
> </wsdl:portType>
>
> <wsdl:binding name="LoginServiceSoapBinding"
> type="impl:LoginServicePortType">
> <wsdlsoap:binding style="document"
> transport="http://schemas.xmlsoap.org/soap/http" />
> <wsdl:operation name="testLogin">
> <wsdlsoap:operation soapAction="" />
> <wsdl:input name="testLoginRequest">
> <wsdlsoap:body use="literal" />
> </wsdl:input>
> <wsdl:output name="testLoginResponse">
> <wsdlsoap:body use="literal" />
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
>
> <wsdl:service name="LoginService">
> <wsdl:port binding="impl:LoginServiceSoapBinding"
> name="LoginService">
> <wsdlsoap:address
> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"
> />
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
>
>
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and CXF - Handling WSDLs differently
Posted by keith chapman <ke...@gmail.com>.
This WSDL looks invalid. As you have said when a message part refers to a
type directly it is RPC whereas when it refers to an element its known as
document. Now the messages parts of your WSDL is RPC but your binsind says
that its document. I feel that the WSDL is incorrect and hence Axis2 is
right in saying that the element is missing.
Thanks,
Keith.
On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <ab...@gmail.com> wrote:
>
> Here is what I found:
> 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java source
> code
> from WSDL file) to generate code from this WSDL, it didn't allow me.
> It kept throwing me an error -
> "An error occurred while completing the process -
> java.lang.InterruptedException
> No element type is defind for the message xxxxx"
> 2.) Then, I switched to CXF 2.0.8 and tried to generate the client
> as I did
> with Axis2 and surprisingly, it got through and created the client side
> stubs.
> CXF doesn't see this WSDL as a bad one.
>
> Please correct me if I'm wrong. To my knowledge, when you
> define "type"
> attribute for the "message" and not the "element" attribute then it has to
> be an "rpc" style.
> Axis2 knows it but CXF ignores it.
>
> Can anyone let me know why there's a difference in handling
> the WSDLs?
> If I modify the WSDL as Axis2 wants me to and generate just
> the client and
> hit the service (which is already existing), will I still be able to
> succeed?
>
> Here is the WSDL I'm talking about:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions targetNamespace="urn:login.safe.two.us"
> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> xmlns:impl="urn:login.safe.two.us"
> xmlns:intf="urn:login.safe.two.us"
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <wsdl:types>
> <schema elementFormDefault="qualified"
> targetNamespace="urn:login.safe.two.us"
> xmlns="http://www.w3.org/2001/XMLSchema">
>
> <complexType name="TestLoginType">
> <sequence>
> <element name="eid" maxOccurs="1"
> minOccurs="1" type="xsd:string" />
> <element name="key" nillable="true"
> type="xsd:string" />
> </sequence>
> </complexType>
>
> <complexType name="TestLoginTypeResponse">
> <sequence>
> <element name="failedReason"
> nillable="true" type="xsd:string" />
> <element name="status"
> type="xsd:boolean" />
> </sequence>
> </complexType>
>
> </schema>
> </wsdl:types>
>
> <wsdl:message name="testLoginRequest">
> <wsdl:part name="testLoginRequestAttributes"
> type="impl:TestLoginType"/>
> </wsdl:message>
>
> <wsdl:message name="testLoginResponse">
> <wsdl:part name="testLoginResponseAttributes"
> type="impl:TestLoginTypeResponse"/>
> </wsdl:message>
>
> <wsdl:portType name="LoginServicePortType">
> <wsdl:operation name="testLogin">
> <wsdl:input message="impl:testLoginRequest"
> name="testLoginRequest" />
> <wsdl:output message="impl:testLoginResponse"
> name="testLoginResponse" />
> </wsdl:operation>
> </wsdl:portType>
>
> <wsdl:binding name="LoginServiceSoapBinding"
> type="impl:LoginServicePortType">
> <wsdlsoap:binding style="document"
> transport="http://schemas.xmlsoap.org/soap/http" />
> <wsdl:operation name="testLogin">
> <wsdlsoap:operation soapAction="" />
> <wsdl:input name="testLoginRequest">
> <wsdlsoap:body use="literal" />
> </wsdl:input>
> <wsdl:output name="testLoginResponse">
> <wsdlsoap:body use="literal" />
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
>
> <wsdl:service name="LoginService">
> <wsdl:port binding="impl:LoginServiceSoapBinding"
> name="LoginService">
> <wsdlsoap:address
> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin" />
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
>
>
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19689331p19689331.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org