Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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:
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";>



ABC123 
KEY123 

  


Response:
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>



soap:Client 
Parameter 
{urn:login.safe.two.us}TestLoginType does not
exist! 

  


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 <[EMAIL PROTECTED]>
> 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 <[EMAIL PROTECTED]>
>> > 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:
>> >>
>> >> 
>> >> > >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> >> ">
>> >>
>> >>
>> >>http://www.w3.org/2001/XMLSchema-instance";
>> >>
>> >> xmlns:s2="http://www.w3.org/2001/XMLSchema";
>> >> s1:type="s2:string">G13522
>> >>http://www.w3.org/2001/XMLSchema-instance";
>> >>
>> >> xmlns:s4="http://www.w3.org/2001/XMLSchema";
>> >> s3:type="s4:string">P9534
>> >>
>> >>
>> >> 
>> >>
>> >>
>> >> Am I missing something here?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Keithgchapman wrote:
>> >> >
>> >> > In your WSDL the parts section look RPC while the binding is
>> document.
>> >> I
>> >> > r

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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 <[EMAIL PROTECTED]>
> 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:
>>
>> 
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> ">
>>
>>
>>http://www.w3.org/2001/XMLSchema-instance";
>>   
>> xmlns:s2="http://www.w3.org/2001/XMLSchema";
>> s1:type="s2:string">G13522
>>http://www.w3.org/2001/XMLSchema-instance";
>>   
>> xmlns:s4="http://www.w3.org/2001/XMLSchema";
>> s3:type="s4:string">P9534
>>
>>
>> 
>>
>>
>> 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 <[EMAIL PROTECTED]>
>> > 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
>> >> > [EMAIL PROTECTED] 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
>> 

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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:


http://schemas.xmlsoap.org/soap/envelope/";>


http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:s2="http://www.w3.org/2001/XMLSchema";
s1:type="s2:string">G13522
http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:s4="http://www.w3.org/2001/XMLSchema";
s3:type="s4:string">P9534





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 <[EMAIL PROTECTED]>
> 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
>> > [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]
>> >> <mailto:[EMAIL PROTECTED]>> 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
>> >> x"
>> >>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 alread

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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 
> [EMAIL PROTECTED] 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 <[EMAIL PROTECTED] 
>> <mailto:[EMAIL PROTECTED]>> 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
>> x"
>>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:
>> 
>> 
>> 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";>
>>
>>>targetNamespace="urn:login.safe.two.us
>> <http://login.safe.two.us>"
>>xmlns="http://www.w3.org/2001/XMLSchema";>
>> 
>>
>>
>>> maxOccurs="1" minOccurs="1" type="xsd:string" />
>>> nillable="true" type="xsd:string" />
>>
>>
>> 
>>
>>
>>> nillable="true" type="xsd:string" />
>>> type="xsd:boolean" />
>>
>>
>> 
>>
>>
>> 
>>
>>> type="impl:TestLoginType"/>
>>
>> 
>>
>>> type="impl:TestLoginTypeResponse"/>
>>
>> 
>>
>>  

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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 <[EMAIL PROTECTED]>
> 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 <[EMAIL PROTECTED]>
>> > 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
>> x"
>> >>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:
>> >>
>> >> 
>> >> > >>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";>
>> >>
>> >>> >>targetNamespace="urn:login.safe.two.us"
>> >>xmlns="http://www.w3.org/2001/XMLSchema";>
>> >>
>> >>
>> >>
>> >>> 

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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 <[EMAIL PROTECTED]>
> 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 x"
>>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:
>>
>> 
>> >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";>
>>
>>>targetNamespace="urn:login.safe.two.us"
>>xmlns="http://www.w3.org/2001/XMLSchema";>
>>
>>
>>
>>> minOccurs="1" type="xsd:string" />
>>> nillable="true"
>> type="xsd:string" />
>>
>>
>>
>>
>>
>>> nillable="true" type="xsd:string" />
>>> type="xsd:boolean" />
>>
>>
>>
>>
>>
>>
>>
>>> type="impl:TestLoginType"/>
>>
>>
>>
>>> type="impl:TestLoginTypeResponse"/>
>>
>>
>>
>>
>>> name="testLoginRequest" />
>>> name="testLoginResponse" />
>>
>>
>>
>>> type="impl:LoginServicePortType">
>>> transport="http://schemas.xmlsoap.org/soap/http"; />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> name="LoginService">
>>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin";
>> />
>>
>>
>> 
>>
>>
>>
>>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: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> 
> blog: http://www.keith-chapman.org
> 
> 

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 and CXF - Handling WSDLs differently

[jackdawson]

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 x"
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:


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";>

http://www.w3.org/2001/XMLSchema";>


































http://schemas.xmlsoap.org/soap/http"; />













http://JISLOGINDEV:8080/JisAuthentication/services/safelogin"; />  


 




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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

_operationClient.addMessageContext(_messageContext) - How to verify

[jackdawson]

Hello,

When the MessageContext object is added to the OperationClient object
(please see 10th statement below) how would I know that it really got added.
I didn't get any AxisFault excpetion which makes me think that it was
successful but I still want to make sure while I debug it. I couldn't find
anything that reflects this added MessageContext object when I debugged the
client stub. 
I'm developing an Axis2 client for an XFire service.

The reason I'm asking this is when the OperationClient executes (please see
11th statement below) I get AxisFault exception.


1.) org.apache.axis2.client.OperationClient _operationClient =
_serviceClient.createClient(_operations[1].getName());

2.) _operationClient.getOptions().setAction("\"\"");

3.) _operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);

4.)addPropertyToOperationClient(_operationClient,org.apache.axis2.description.WSDL2Constants.ATTR_WHTTP_QUERY_PARAMETER_SEPARATOR,"&");
  
5.) // create a message context
_messageContext = new org.apache.axis2.context.MessageContext();

6.) // create SOAP envelope with that payload
org.apache.axiom.soap.SOAPEnvelope env = null;  
  
7.)  env =
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
  testLoginType2,
  optimizeContent(new javax.xml.namespace.QName("urn:login.safe.two.us",
"testLogin")));

8.) //adding SOAP soap_headers
_serviceClient.addHeadersToEnvelope(env);

9.) // set the message context with that soap envelope
_messageContext.setEnvelope(env);

10.) // add the message context to the operation client
 _operationClient.addMessageContext(_messageContext);  

11.) //execute the operation client
 _operationClient.execute(true);


The exception I get:
org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
does not exist!
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)

Hope someone knows what I'm talking about.
Any help is appreciated.

Thanks.
-- 
View this message in context: 
http://www.nabble.com/_operationClient.addMessageContext%28_messageContext%29---How-to-verify-tp19677300p19677300.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problem with Axis2 client and XFire service

[jackdawson]

Thanks Martin. You are quick. I really appreciate it.
Please let me know what should go inside
_operationClient.getOptions().setAction("");
Here is the WSDL:


http://xml.apache.org/xml-soap";
xmlns:impl="urn:login.safe.two.us"
xmlns:intf="urn:login.safe.two.us"
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>


http://www.w3.org/2001/XMLSchema";>   




























 










http://schemas.xmlsoap.org/soap/http"/>












   
http://JISAUTHDEV:8185/JisAuthentication/services/authorization"/>








Thanks.





































mgainty wrote:
> 
> 
> the action name you supplied looks problematic
> it should look something like
> try
> {
>org.apache.axis2.client.OperationClient _operationClient =
> _serviceClient.createClient(_operations[0].getName());
>  
> _operationClient.getOptions().setAction("http://www.example.com/OnlineBooksADBImage/FindBooks";);
> }
> catch(org.apache.axis2.AxisFault f)
> {
>log.debug("AxisFault has been thrown ..");
> }
> in any event could you please post your WSDL 
> 
> thanks,
> Martin 
> __ 
> Disclaimer and confidentiality note 
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and
> Sender does not endorse distribution to any party other than intended
> recipient. Sender does not necessarily endorse content contained within
> this transmission. 
> 
> 
>> Date: Mon, 22 Sep 2008 06:28:45 -0700
>> From: [EMAIL PROTECTED]
>> To: axis-user@ws.apache.org
>> Subject: RE: Problem with Axis2 client and XFire service
>> 
>> 
>> Thanks Martin.
>> 
>> Actually, I'm using Eclipse with Axis2 Codegen plugins. When I created
>> client using it, this is what it created as the stub:
>> (I'm pasting only the operation "testLogin" implementation from the
>> stub).
>> Please let me know if you want me to post my WSDL.
>> 
>> /**
>>  * Auto generated method signature
>>  *
>>  * @see us.two.safe.login.LoginService#testLogin
>>  * @param testLoginType0
>>  */
>> 
>>  public 
>> us.two.safe.login.LoginServiceStub.TestLoginTypeResponse testLogin(
>>us.two.safe.login.LoginServiceStub.TestLoginType
>> testLoginType0) throws java.rmi.RemoteException
>>
>>   {
>>   org.apache.axis2.context.MessageContext _messageContext =
>> null;
>>   try{
>> org.apache.axis2.client.OperationClient _operationClient
>> =
>>
>> _serviceClient.createClient(_operations[0].getName());
>> _operationClient.getOptions().setAction("\"\"");
>>  
>> _operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);
>> 
>> addPropertyToOperationClient(_operationClient,org.apache.axis2.description.WSDL2Constants.ATTR_WHTTP_QUERY_PARAMETER_SEPARATOR,"&");
>> 
>>   // create a message context
>>   _messageContext = new
>> org.apache.axis2.context.MessageContext();
>>  
>> 
>>   // create SOAP envelope with that payload
>>   org.apache.axiom.soap.SOAPEnvelope env = null;
>>
>>   env =
>> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
>> testLoginType0,
>> optimizeContent(new
>> javax.xml.namespace.QName("

RE: Problem with Axis2 client and XFire service

[jackdawson]

Thanks Martin.

Actually, I'm using Eclipse with Axis2 Codegen plugins. When I created
client using it, this is what it created as the stub:
(I'm pasting only the operation "testLogin" implementation from the stub).
Please let me know if you want me to post my WSDL.

/**
 * Auto generated method signature
 *
 * @see us.two.safe.login.LoginService#testLogin
 * @param testLoginType0
 */

 public 
us.two.safe.login.LoginServiceStub.TestLoginTypeResponse testLogin(
   us.two.safe.login.LoginServiceStub.TestLoginType
testLoginType0) throws java.rmi.RemoteException
   
  {
  org.apache.axis2.context.MessageContext _messageContext =
null;
  try{
org.apache.axis2.client.OperationClient _operationClient =
   
_serviceClient.createClient(_operations[0].getName());
_operationClient.getOptions().setAction("\"\"");
 
_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);

addPropertyToOperationClient(_operationClient,org.apache.axis2.description.WSDL2Constants.ATTR_WHTTP_QUERY_PARAMETER_SEPARATOR,"&");

  // create a message context
  _messageContext = new
org.apache.axis2.context.MessageContext();
 

  // create SOAP envelope with that payload
  org.apache.axiom.soap.SOAPEnvelope env = null;
   
  env =
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
testLoginType0,
optimizeContent(new
javax.xml.namespace.QName("urn:login.safe.two.us",
"testLogin")));
 
  //adding SOAP soap_headers
  _serviceClient.addHeadersToEnvelope(env);

  // set the message context with that soap envelope
  _messageContext.setEnvelope(env);

 // add the message contxt to the operation client
 _operationClient.addMessageContext(_messageContext);

 //execute the operation client
 _operationClient.execute(true);

 org.apache.axis2.context.MessageContext _returnMessageContext =
_operationClient.getMessageContext(
  
org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);
 org.apache.axiom.soap.SOAPEnvelope _returnEnv =
_returnMessageContext.getEnvelope();
   
   
 java.lang.Object object =
fromOM(_returnEnv.getBody().getFirstElement() ,
   
two.safe.login.LoginServiceStub.TestLoginTypeResponse.class,
 
getEnvelopeNamespaces(_returnEnv));

   
 return
(us.two.safe.login.LoginServiceStub.TestLoginTypeResponse)object;
   
 }
catch(org.apache.axis2.AxisFault f){

org.apache.axiom.om.OMElement faultElt = f.getDetail();
if (faultElt!=null){
if (faultExceptionNameMap.containsKey(faultElt.getQName())){
//make the fault by reflection
try{
java.lang.String exceptionClassName =
(java.lang.String)faultExceptionClassNameMap.get(faultElt.getQName());
java.lang.Class exceptionClass =
java.lang.Class.forName(exceptionClassName);
java.lang.Exception ex=
(java.lang.Exception)
exceptionClass.newInstance();
//message class
java.lang.String messageClassName =
(java.lang.String)faultMessageMap.get(faultElt.getQName());
java.lang.Class messageClass =
java.lang.Class.forName(messageClassName);
java.lang.Object messageObject =
fromOM(faultElt,messageClass,null);
java.lang.reflect.Method m =
exceptionClass.getMethod("setFaultMessage",
   new java.lang.Class[]{messageClass});
m.invoke(ex,new java.lang.Object[]{messageObject});
   

throw new java.rmi.RemoteException(ex.getMessage(),
ex);
}catch(java.lang.ClassCastException e){
   // we cannot intantiate the class - throw the
original Axis fault
throw f;
} catch (java.lang.ClassNotFoundException e) {
// we cannot intantiate the class - throw the
original Axis fault
throw f;
}catch (java.lang.NoSuchMethodException e) {
//

RE: Problem with Axis2 client and XFire service

[jackdawson]

Thanks Martin.

Actually, I'm using Eclipse with Axis2 Codegen plugins. When I created
client using it, this is what it created as the stub:
(I'm pasting only the operation "testLogin" implementation from the stub). 
Please let me know if you want me to post my WSDL.

/**
 * Auto generated method signature
 * 
 * @see us.two.safe.login.LoginService#testLogin
 * @param testLoginType0
 */

 public 
us.two.safe.login.LoginServiceStub.TestLoginTypeResponse testLogin(
   us.two.safe.login.LoginServiceStub.TestLoginType
testLoginType0) throws java.rmi.RemoteException

  {
  org.apache.axis2.context.MessageContext _messageContext =
null;
  try{
org.apache.axis2.client.OperationClient _operationClient = 

_serviceClient.createClient(_operations[0].getName());
_operationClient.getOptions().setAction("\"\"");
  
_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);

addPropertyToOperationClient(_operationClient,org.apache.axis2.description.WSDL2Constants.ATTR_WHTTP_QUERY_PARAMETER_SEPARATOR,"&");

  // create a message context
  _messageContext = new
org.apache.axis2.context.MessageContext();
  

  // create SOAP envelope with that payload
  org.apache.axiom.soap.SOAPEnvelope env = null;

  env =
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
testLoginType0,
optimizeContent(new
javax.xml.namespace.QName("urn:login.safe.two.us",
"testLogin")));
  
  //adding SOAP soap_headers
  _serviceClient.addHeadersToEnvelope(env);

  // set the message context with that soap envelope
  _messageContext.setEnvelope(env);

 // add the message contxt to the operation client
 _operationClient.addMessageContext(_messageContext);

 //execute the operation client
 _operationClient.execute(true);

 org.apache.axis2.context.MessageContext _returnMessageContext =
_operationClient.getMessageContext(
  
org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);
 org.apache.axiom.soap.SOAPEnvelope _returnEnv =
_returnMessageContext.getEnvelope();


 java.lang.Object object =
fromOM(_returnEnv.getBody().getFirstElement() ,

two.safe.login.LoginServiceStub.TestLoginTypeResponse.class,
 
getEnvelopeNamespaces(_returnEnv));

   
 return
(us.two.safe.login.LoginServiceStub.TestLoginTypeResponse)object;
   
 }
catch(org.apache.axis2.AxisFault f){

org.apache.axiom.om.OMElement faultElt = f.getDetail();
if (faultElt!=null){
if (faultExceptionNameMap.containsKey(faultElt.getQName())){
//make the fault by reflection
try{
java.lang.String exceptionClassName =   

(java.lang.String)faultExceptionClassNameMap.get(faultElt.getQName());
java.lang.Class exceptionClass =
java.lang.Class.forName(exceptionClassName);
java.lang.Exception ex=
(java.lang.Exception)
exceptionClass.newInstance();
//message class
java.lang.String messageClassName =
(java.lang.String)faultMessageMap.get(faultElt.getQName());
java.lang.Class messageClass =
java.lang.Class.forName(messageClassName);
java.lang.Object messageObject =
fromOM(faultElt,messageClass,null);
java.lang.reflect.Method m =
exceptionClass.getMethod("setFaultMessage",
   new java.lang.Class[]{messageClass});
m.invoke(ex,new java.lang.Object[]{messageObject});


throw new java.rmi.RemoteException(ex.getMessage(),
ex);
}catch(java.lang.ClassCastException e){
   // we cannot intantiate the class - throw the
original Axis fault
throw f;
} catch (java.lang.ClassNotFoundException e) {
// we cannot intantiate the class - throw the
original Axis fault
throw f;
}catch

Problem with Axis2 client and XFire service

[jackdawson]

Hi,

I created an Axis2 client for an XFire service. But something seems to be
wrong. 
When I run the client this is what I get.

org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
does not exist!
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)

I debugged the client and found that the error occurs when this statement is
executed in the stub:

//execute the operation client
_operationClient.execute(true);

Can anyone let me know is it the client that is weird or the service?


Thanks.
-- 
View this message in context: 
http://www.nabble.com/Problem-with-Axis2-client-and-XFire-service-tp19575959p19575959.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: AW: IWAB0497E Error in writing WSDL file null

[jackdawson]

No, I didn't follow the instructions from there. 
This is where I followed the steps from : 
http://wso2.org/library/1986 http://wso2.org/library/1986 

But I think I'm kind of lost now. Before I ask you why JIBX came into
picture may I ask you the steps to create a web service when you have only
WSDL. I rehearsed creating web services by using lots of WSDLs from
XMethods.com and they worked fine. 

I'm sure something is hiding here with this case which I can't trace. For
now, I think it's all in the WSDL I'm using but I may be something else too.

Thanks.  
-- 
View this message in context: 
http://www.nabble.com/IWAB0497E-Error-in-writing-WSDL-file-null-tp19529642p19545390.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AW: IWAB0497E Error in writing WSDL file null

[jackdawson]

Thanks for the prompt reply.

I'm using Axis2 Eclipse Codegen plugin for creating a web service from a
WSDL.

Initially, I tried to create server side components. So, this is what I did:
Step 1: File -> New -> Other ->Axis2 Wizards -> Axis2 Code Generator.
Clicked Next.
Step 2: Selected "Generate Java source code from a WSDL file". Clicked Next.
Step 3: Selected the WSDL file location and clicked Next.
Step 4: Selected "Codegen Option" as "custom" and selected the checkbox
"Generate server side code" and "Generate a default services.xml". Clicked
Next. 
Step 5: Selected the radio option "Browse and select a project on current
eclipse workspace" and specified the project. I even selected the checkbox
"Add the Axis2 codegen jars to the codegen resulted project".
Step 6: Clicked Finish. Not a happy ending. It threw me an
InterruptedException.

Here is the WSDL that I used to generate the java code:
The  element inside  seems to be the culprit. When I comment
both the request and response  elements I won't get any error.



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";>

http://www.w3.org/2001/XMLSchema";>






















 










http://schemas.xmlsoap.org/soap/http"; />












  
http://localhost:8080/axis2/services/login";
/>  





This is what the exception raised:
An error occurred while completing process -
java.lang.reflect.InvocationException
No element type is defined for the message testLoginRequest

Any help is really appreciated.

Thanks.


 
-- 
View this message in context: 
http://www.nabble.com/IWAB0497E-Error-in-writing-WSDL-file-null-tp19529642p19537249.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AW: IWAB0497E Error in writing WSDL file null

[jackdawson]

Thanks Markus but there are folders and no content under WebContent.

I thought it would be easier to use Axis2 Eclipse Codegen plugins. Even that
threw an InterruptedException on the final step of generating server side
stuff.

Any idea of what might be wrong?

Thanks.






Grimm, Markus wrote:
> 
> Hi,
> 
> just an idea: is there a resource-folder under your project ? delete all
> content.
> delete all content under WebContent except axis2-web, META-INF and
> WEB-INFand try again.
> 
> hope this helps...
> 
> Bye
> Markus
> 
> 
> 
>  
> 
> 
> 
> -Ursprüngliche Nachricht-
> Von: jackdawson [mailto:[EMAIL PROTECTED] 
> Gesendet: Mittwoch, 17. September 2008 13:09
> An: axis-user@ws.apache.org
> Betreff: IWAB0497E Error in writing WSDL file null
> 
> 
> Hello all,
> 
> First of all thanks for all the help I've been getting here. 
> Here is the new hurdle. I followed all the steps for creating a web
> service
> using a top down approach from this tutorial: 
> 
> http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebService/td_tutorial.html
> http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebService/td_tutorial.html
>  
> 
> But after the step12 I got the error below. It couldn't parse the WSDL and
> generate the service. 
> I'm using:
> 1) Eclipse WTP 3.3.x 
> 2) Axis2 1.4.1
> 3)Tomcat 6
> 4) JDK 1.5
> 
> Does anyone know what exactly this means?
> 
> IWAB0497E Error in writing WSDL file null
> org.eclipse.core.internal.resources.ResourceException: A resource
> exists
> with a different case: '/TestAuthenticationWebService/WebContent/WSDL'.
> at
> org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:298)
> at
> org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:276)
> at
> org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:29)
> at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
> at org.eclipse.core.internal.resources.Folder.create(Folder.java:118)
> at
> org.eclipse.jst.ws.internal.axis.consumption.ui.util.FileUtil.createFolder(FileUtil.java:102)
> at
> org.eclipse.jst.ws.internal.axis.creation.ui.task.Skeleton2WSDLCommand.execute(Skeleton2WSDLCommand.java:173)
> at
> org.eclipse.jst.ws.internal.axis.creation.ui.command.TDCodeGenOperation$TopDownWSModifyOperation.execute(TDCodeGenOperation.java:151)
> at
> org.eclipse.jst.ws.internal.axis.creation.ui.command.TDCodeGenOperation.execute(TDCodeGenOperation.java:89)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at
> org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at
> org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
> at
> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at
> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at
> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:182)
> at org.eclipse.

IWAB0497E Error in writing WSDL file null

[jackdawson]

Hello all,

First of all thanks for all the help I've been getting here. 
Here is the new hurdle. I followed all the steps for creating a web service
using a top down approach from this tutorial: 

http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebService/td_tutorial.html
http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebService/td_tutorial.html
 

But after the step12 I got the error below. It couldn't parse the WSDL and
generate the service. 
I'm using:
1) Eclipse WTP 3.3.x 
2) Axis2 1.4.1
3)Tomcat 6
4) JDK 1.5

Does anyone know what exactly this means?

IWAB0497E Error in writing WSDL file null
org.eclipse.core.internal.resources.ResourceException: A resource exists
with a different case: '/TestAuthenticationWebService/WebContent/WSDL'.
at
org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:298)
at
org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:276)
at
org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:29)
at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
at org.eclipse.core.internal.resources.Folder.create(Folder.java:118)
at
org.eclipse.jst.ws.internal.axis.consumption.ui.util.FileUtil.createFolder(FileUtil.java:102)
at
org.eclipse.jst.ws.internal.axis.creation.ui.task.Skeleton2WSDLCommand.execute(Skeleton2WSDLCommand.java:173)
at
org.eclipse.jst.ws.internal.axis.creation.ui.command.TDCodeGenOperation$TopDownWSModifyOperation.execute(TDCodeGenOperation.java:151)
at
org.eclipse.jst.ws.internal.axis.creation.ui.command.TDCodeGenOperation.execute(TDCodeGenOperation.java:89)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
at
org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:182)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
   

Re: InterruptedException with Eclipse Codegen plug-in

[jackdawson]

Hello all,

Can anyone tell me what is wrong with this WSDL? 
Why am I getting the InterruptedException when I try to generate server side
stuff using the Axis2 Eclipse Codegen plugin wizard?


http://xml.apache.org/xml-soap";
xmlns:impl="urn:a.b.c.d"
xmlns:intf="urn:a.b.c.d"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

http://www.w3.org/2001/XMLSchema";>




















 



   



  











  





















http://schemas.xmlsoap.org/soap/http"; />













http://localhost:8080/loginauth/services/auth"; />




I appreciate for your time.

Thanks.






jackdawson wrote:
> 
> Hi,
> 
> I'm trying to generate server side stuff and server.xml from a WSDL using
> Axis2 Eclipse Codegen plug-in but when I clicked Finish on the final page
> it kicked me with this error:
> 
> An error occured while completing process- java.lang.
> http://www.nabble.com/file/p19417409/InterruptedException.doc
> InterruptedException.doc :
> No element type is defined for message loginRequest
> 
> I attached even the screenshot.
> 
> It seems that its because of the WSDL. Am I right?
> Did anyone face this issue before? Does anyone know what then ext step
> would be?
> 
> Here is the sample wsdl I used.
>  http://www.nabble.com/file/p19417409/LoginService.wsdl LoginService.wsdl 
> 
> Thanks in advance.
> 

-- 
View this message in context: 
http://www.nabble.com/InterruptedException-with-Eclipse-Codegen-plug-in-tp19417409p19448192.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

InterruptedException with Eclipse Codegen plug-in

[jackdawson]

Hi,

I'm trying to generate server side stuff and server.xml from a WSDL using
Axis2 Eclipse Codegen plug-in but when I clicked Finish on the final page it
kicked me with this error:

An error occured while completing process- java.lang.
http://www.nabble.com/file/p19417409/InterruptedException.doc
InterruptedException.doc :
No element type is defined for message loginRequest

I attached even the screenshot.

It seems that its because of the WSDL. Am I right?
Did anyone face this issue before? Does anyone know what then ext step would
be?

Thanks in advance.
-- 
View this message in context: 
http://www.nabble.com/InterruptedException-with-Eclipse-Codegen-plug-in-tp19417409p19417409.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis Fault exception

[jackdawson]

But my company has all of its web services in Axis 1.2
Do you think we are in the ancient ages? 

I have a WSDL of other team's web service and I generated client side stubs
and developed a simple java app client. And, when I run the client this is
what getting thrown. Did I miss any step?

Thanks.





keith chapman wrote:
> 
> Could you try this with Axis2 instead. If you are a newbie to axis
> then I recommend you to use Axis2 instead of Axis2.
> 
> Thanks,
> Keith.
> 
> On Sat, Aug 30, 2008 at 12:11 AM, unbeatable <[EMAIL PROTECTED]>
> wrote:
>>
>>
>>
>> Hi,
>>
>> I was trying to play with Web Services and Apache Axis. What I did was I
>> grabbed the WSDL file of a web service built using XFire and tried to
>> generate client side stubs and interfaces. I was successful in that.
>> Then, I
>> developed a client class for this, a simple java app. Until this point,
>> everything seems fine.
>>
>> Then started the hurdles. I ran the client and it threw me an Axis Fault
>> exception. Its throwing the erro when I invoke the service.
>>
>> This is what I did in the client:
>>
>>StockSoapBindingStub stub = new StockSoapBindingStub(
>>new URL("http://";),
>>new Stock_ServiceLocator());
>>String stock = stub.testStock();
>>
>>
>>
>> AxisFault
>>  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
>>  faultSubcode:
>>  faultString: Parameter testStockAttributes does not exist!
>>  faultActor:
>>  faultNode:
>>  faultDetail:
>>{http://xml.apache.org/axis/}stackTrace:Parameter
>> testStockAttributes does
>> not exist!
>>at
>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>at
>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>at
>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>>at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>>at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>>at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>>at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>>at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>>at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>>at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>>at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>>at
>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>>at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>>at
>> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
>>at
>> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
>>at
>> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>>at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>>at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>at org.apache.axis.client.Call.invoke(Call.java:2767)
>>at org.apache.axis.client.Call.invoke(Call.java:2443)
>>at org.apache.axis.client.Call.invoke(Call.java:2366)
>>at org.apache.axis.client.Call.invoke(Call.java:1812)
>>
>> Does anyone have an idea why this exception has to show up?
>> Thanks in advance.
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis-Fault-exception-tp19225005p19225005.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> -- 
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> 
> blog: http://www.keith-chapman.org
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis-Fault-exception-tp19225005p19405443.html

Re: fault string: parameter xxxx doesn't exist

[jackdawson]

Thanks Keith.
But I couldn't get the TCP/IP monitor to work.
If this is the endpoint address,
http://www.interpressfact.net/webservices/getJoke.asmx ,
how would I set up TCP/IP monitor. I want to try with external web services
first.

I generated the client side stubs using their WSDL and I only have the
client on my side.

Thanks.








keith chapman wrote:
> 
> Hi,
> 
> Can you use TCPMonitor to capture the messages you sent to the service.
> You
> may use this blog post which describes how you can set up TCPMonitor to
> debug.
> 
> If you send the request and response together with the WSDL that will help
> us point you to the exact issue. Looking at your stack trace it looks like
> the error occurs when reading in the response and not sending the request.
> 
> BTW it also looks as though you are using Axis. If you are new to Axis
> land
> then I recommend you use Axis2 instead of Axis. You can get Axis2 from
> http://ws.apache.org/axis2/
> 
> Thanks,
> Keith.
> 
> On Tue, Sep 2, 2008 at 1:15 AM, Abhishek Kaukuntla
> <[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>> When I ran the class in the debug mode and traced I could see the
> parameter
>> with the right value when the service is invoked. I don't know where it
> went
>> wrong. I'm at home so I don't have the WSDL with me now.
>>
>> This is what I did.
>>
>> I grabbed the WSDL file of a web service built using XFire and tried to
>> generate client side stubs and interfaces. I was successful in that.
>> Then,
> I
>> developed a client class for this, a simple java app. Until this point,
>> everything seems fine.
>>
>> Then started the hurdles. I ran the client and it threw me an Axis Fault
>> exception. Its throwing the error when I invoke the service.
>>
>> This is what I did in the client:
>>
>>StockSoapBindingStub stub = new StockSoapBindingStub(
>>new URL("http://";),
>>new Stock_ServiceLocator());
>>String stock = stub.testStock();
>>
>>
>>
>> AxisFault
>>  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
>>  faultSubcode:
>>  faultString: Parameter testStockAttributes does not exist!
>>  faultActor:
>>  faultNode:
>>  faultDetail:
>>   
>> {http://xml.apache.org/axis/}stackTrace:ParametertestStockAttributes
>> does
>> not exist!
>>at
>>
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>at
>>
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>at
>>
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>at
>>
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>>at
>>
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>>at
>>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>>at
>>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>>at
>>
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>>at
>>
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>>at
>>
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>>at
>>
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>>at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>>at
>>
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>>at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>>at
>>
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
>>at
>> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
>>at
>>
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>>at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>>at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>at org.apache.axis.client.Call.invoke(Call.java:2767)
>>at org.apache.axis.client.Call.invoke(Call.java:2443)
>>at org.apache.axis.client.Call.invoke(Call.java:2366)
>>at org.apache.axis.client.Call.invoke(Call.java:1812)
>>
>> Can you let me know what did I do wrong for the exception to show up?
>> Thanks.
>>
>>
>>
>>
>> On Mon, Sep 1, 2