axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilina Gunarathne (JIRA)" <>
Subject [jira] Commented: (AXIS2-3196) .NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
Date Thu, 08 Nov 2007 16:01:53 GMT


Thilina Gunarathne commented on AXIS2-3196:

As I said above try replacing the Axiom jars in the Axis2 1.3 with the latest snaphots. ...

> .NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
> ---------------------------------------------------------------
>                 Key: AXIS2-3196
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: OS: Windows XP
> Client: .NET 2.0 C# via WSE 3.0
> Server: Axis2.0 Version 1.3 on JBoss Application Server 4.0.5.GA via Java 1.5 
>            Reporter: james chan
>            Assignee: Thilina Gunarathne
> Hi,
> I am writing a .NET client application that calls a web method from an Axis2.0 (version
1.3) server. My method simply get a text file from the server as an MTOM attachment. When
the web method is done executing, the following exception is thrown:
> WSE1621: The incoming message doesn't have the SOAP envelope as the first MIME part as
required for security purposes. Refer to the messaging/mtom/requireSoapEnvelopeFirst configuration
section to turn this off. It is recommended to turn this on for security reasons.
> I proceed to uncheck the "Require SOAP Envelope First" option and re-run my client code.
I get the following exception:
>  WSE1608: No XOP parts were located in the stream for the specified content-id:
>  I use TCPMON to inspect the response header (see below) and can verify that the content-id
does have a XOP definition.
> Upon closer inspection of the SOAP response header (see below), The value of the "start"
attribute should match the value of the "content-id". The value of the content-id of the first
MIME boundary is "<>" and the start
attribute is "". It is clear that content-id
attribute and start attribute do not match because of the missing "<" and ">".  This
is why the exception reads "no xop parts where located for the specified content-id". It could
not find that content-id!
> The same .NET client works under Axis2.0 (version 1.2). The content-id and start attribute
both contains the "<" and ">" character in the response message.
> Please fix this as soon as possible!!
> Thanks.
> *******************************************************************************************************************************************************************
> Server: Apache-Coyote/1.1
> X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
> Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250;
type="application/xop+xml"; start="";
start-info="application/soap+xml"; action="urn:getMTOMAttachmentResponse"
> Transfer-Encoding: chunked
> Date: Wed, 12 Sep 2007 17:58:39 GMT
> 405
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> Content-Type: application/xop+xml; charset=utf-8; type="application/soap+xml"
> Content-Transfer-Encoding: binary
> Content-ID: <>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv=""
xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href=""
xmlns:xop="" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <>
> This is a test for Web Service using Axis2.0 via MTOM attachments
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> 2
> --
> 0

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message