Good Evening
if you publish your wsdl we can run the client code
Thanks
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Ted Jones" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, May 09, 2007 7:10 PM
Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
So, I'm guessing that the message is never reaching the server. Which
may explain why there is no logging? I can see in debug where the
Sandesha2 logic is hit and the message is sent but I never see any
sequences or other message traffic and my client is left polling forever
waiting for the callback to complete.
Any other thoughts on what might be happening here or where else I can
look?
Thanks,
Ted
-----Original Message-----
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 10:27 AM
To: [email protected]
Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Thanks for all the responses. This is a great mailing list.
I am not seeing any messages in TCPMON or in the logs. :-(
Question: How can you configure TCPMON to capture messages sent to
SimpleHTTPServer? I get a port bind exception.
Also, I cannot seems to get logging working with Sandesha2. If anyone
has it working, I would really appreciate a peek at their
log4j.properties.
Thanks!
Ted
-----Original Message-----
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 11:12 PM
To: [email protected]
Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Ted Jones wrote:
I am using Sandesha2 with an asynch Axis2 client. Using the example
that comes with Sandesha2 (the asynch echo client), the onComplete()
method of my callback is never hit. It appears the response is not
returning.
Any ideas?
Did you try capturing message sequences with TCPMON and chek the message
sequence?
Also, have a look into the server and client logs.
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
