Problem description
--
When I call .NET service ( Visual Studio 2005 ) using
Axis2-generated client I got exception:
Exception in thread "main" org.apache.axis2.AxisFault: The input
stream for an incoming message is null.
at
org.apache.axis2.transport.Transpor
Maxim
What version of .NET is this? I notice that the SOAP 1.1 calls are all
working and SOAP1.2 isn't.
Try
stub._getServiceClient().getOptions().setSoapVersionURI(
org.apache.axis2.namespace.Constants.URI_SOAP11_ENV);
Paul
On 10/26/07, Maxim Geraskyn <[EMAIL PROTECTED]> wrote:
>
> > Is there
Is there any error log on the .NET side?
I can't see anything really wrong with the Axis2 request. How did you
generate the client?
Paul
On 10/26/07, Maxim Geraskyn <[EMAIL PROTECTED]> wrote:
>
> Problem description
> --
> When I call .NET service ( Visual Stu
> Is there any error log on the .NET side?
Hmm, may be, have to check
> I can't see anything really wrong with the Axis2 request. How did you
> generate the client?
As I mentioned xml part of request is fine. If I change headers it
works perfectly.
Client was generated by WSDL2Java
va utility
Suggest going to JIRA for more info
http://issues.apache.org/jira/browse/AXIS2
Anyone else?
HTH/
Martin--
Original Message -
From: "Maxim Geraskyn" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 26, 2007 5:30 AM
Subject: AXIS2 and .NET Inter
be a bug in WSDL2Java utility
> Suggest going to JIRA for more info
> http://issues.apache.org/jira/browse/AXIS2
>
> Anyone else?
> HTH/
> Martin--
> Original Message -
> From: "Maxim Geraskyn" <[EMAIL PROTECTED]>
> To:
> Sent: Friday, October 2
Paul,
> What version of .NET is this?
I'm using Visual Studio 2005, .NET Framework v2.0.50727
> Try
>
> stub._getServiceClient().getOptions().setSoapVersionURI(org.apache.axis2.namespace.Constants.URI_SOAP11_ENV
> );
Hmm, same result
Request:
PO
Maybe its HTTP chunking? I notice that the working versions don't use that.
Try turning it off like this:
stub.getServiceClient().getOptions().setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED,
Boolean.FALSE);
Paul
On 10/26/07, Maxim Geraskyn <[EMAIL PROTECTED]> wrote:
>
> Paul
Paul,
> Maybe its HTTP chunking? I notice that the working versions don't use that.
>
> Try turning it off like this:
now it works, soap12 calls work also, so my problem was caused by
"chunked" encoding.
-
To unsubscribe, e-mail
> now it works, soap12 calls work also, so my problem was caused by
> "chunked" encoding.
I double checked, when I comment out
stub._getServiceClient().getOptions().setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED
,
Boolean.FALSE);
it stops working
Thanks for your help, Paul !
No problem!
I'm surprised .NET can't handle HTTP chunking... its a common approach.
Paul
On 10/28/07, Maxim Geraskyn <[EMAIL PROTECTED]> wrote:
>
> > now it works, soap12 calls work also, so my problem was caused by
> > "chunked" encoding.
>
> I double checked, when I comment out
>
> stub._getSe
To: axis-user@ws.apache.org
Sent: Sunday, October 28, 2007 9:01 AM
Subject: Re: AXIS2 and .NET Interop
No problem!
I'm surprised .NET can't handle HTTP chunking... its a common approach.
Paul
On 10/28/07, Maxim Geraskyn < [EMAIL PROTECTED]> wrote:
> now it
Paul,
> I'm surprised .NET can't handle HTTP chunking... its a common approach.
>
> Paul
I'm not so experienced in web technologies, but this is the first time
I see SOAP client uses "chunked". Normally "content-length" header is
used by default ( AXIS 1.*, SoapUI, .NET )
Maxim
13 matches
Mail list logo