Re: Axis2 .NETproblem

Tue, 06 Jun 2006 20:34:37 -0700

Hi,
AFAIK http 100 is not a prob..  It's how .net greets and welcome the incoming messages ;)...
Seems like .net client is having the prob. I can't notice the prob straight away.. Somebody with .net experience might be able to comment on this..
Try switching of addressing on the client side - just a thought since java client is not using addressing..
 
Try debugging the client to get to the exact prob...May be with what Jim suggested...
 
Thanks,
~Thilina

 
On 6/7/06, Jim Collins <[EMAIL PROTECTED]> wrote:
Hi Bob,
 
I have not written the .NET client but I do know that he is using .NET 2.0 and WSE 3. I will pass on your suggestions to turn on diagnostic messaging.
 
Regards
 
Jim
----- Original Message -----
Sent: Tuesday, June 06, 2006 12:05 PM
Subject: RE: Axis2 .NETproblem

 
To help diagnose the .NET side of things, you may wish to turn on diagnostics.  If you're .NET client is using .NET 2.0, then install WSE3, enable WSE3 on the project, and turn on the diagnostic messaging.  If you using WinFX, then use the SvcConfigEditor to turn on client-side diagnostics.  This may help see what's going on under the hood.
 
regards,
bob

From: Jim Collins [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 06, 2006 1:00 AM
To: [email protected]
Subject: Re: Axis2 .NETproblem

 
Hi Thilina,
 
I will send the TCPMON snapshots later. I am not sure that there are any stack traces from the .NET client. As far as I am aware the client calls the operation and the return object that is null.
 
Regards
 
Jim
----- Original Message -----
Sent: Tuesday, June 06, 2006 3:15 AM
Subject: Re: Axis2 .NETproblem

 
Can you post the message snaphots from TCPMON and the exact stack trace .net gave...
 
Thanks,
~Thilina
 
On 6/6/06, Jim Collins <[EMAIL PROTECTED] > wrote:
Hi all,
 
I have a simple web service for uploading and downloading files that is MTOM enabled. I have used it with no problems from a Java client but there are problems with a .NET client. I have the TCP monitor and the .NET client calls a connection operation that returns a simple string. The server can see the call OK and returns the string and I can see all of this happening from the TCP monitor. However the .NET client complains of a null error that nothing was returned.
 
Does anyone have any idea what could be causing this.
 
Regards
 
Jim



--
"May the SourcE be with u"            
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/                 http://www.bloglines.com/blog/Thilina              



--
"May the SourcE be with u"            
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/                 http://www.bloglines.com/blog/Thilina              

Reply via email to