You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "james chan (JIRA)" <ji...@apache.org> on 2007/09/12 20:09:32 UTC
[jira] Created: (AXIS2-3196) .NET C# using WSE 3.0 does not interop
with Axis2.0 Version 1.3
.NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
---------------------------------------------------------------
Key: AXIS2-3196
URL: https://issues.apache.org/jira/browse/AXIS2-3196
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
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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
*******************************************************************************************************************************************************************
RESPONSE HEADER viewed from TCPMON
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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
38
--MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
c7
Content-Type: text/plain
Content-Transfer-Encoding: binary
Content-ID: <1....@apache.org>
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3196) .NET C# using WSE 3.0 does not
interop with Axis2.0 Version 1.3
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541070 ]
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: https://issues.apache.org/jira/browse/AXIS2-3196
> 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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
> 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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
>
> *******************************************************************************************************************************************************************
> RESPONSE HEADER viewed from TCPMON
> 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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <1....@apache.org>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-3196) .NET C# using WSE 3.0 does not
interop with Axis2.0 Version 1.3
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thilina Gunarathne reassigned AXIS2-3196:
-----------------------------------------
Assignee: Thilina Gunarathne
> .NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
> ---------------------------------------------------------------
>
> Key: AXIS2-3196
> URL: https://issues.apache.org/jira/browse/AXIS2-3196
> 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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
> 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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
>
> *******************************************************************************************************************************************************************
> RESPONSE HEADER viewed from TCPMON
> 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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <1....@apache.org>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3196) .NET C# using WSE 3.0 does not
interop with Axis2.0 Version 1.3
Posted by "Raag Bansal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556891#action_12556891 ]
Raag Bansal commented on AXIS2-3196:
------------------------------------
Sorry to ask this but I couldn't locate latest axiom jars in the nightly builds for axis2. Could you please help me get the latest axiom-api jar since I too get the problem related to angle brackets?
Thanks in advance.
> .NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
> ---------------------------------------------------------------
>
> Key: AXIS2-3196
> URL: https://issues.apache.org/jira/browse/AXIS2-3196
> 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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
> 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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
>
> *******************************************************************************************************************************************************************
> RESPONSE HEADER viewed from TCPMON
> 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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <1....@apache.org>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3196) .NET C# using WSE 3.0 does not
interop with Axis2.0 Version 1.3
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533582 ]
Thilina Gunarathne commented on AXIS2-3196:
-------------------------------------------
Found the culprit..
http://svn.apache.org/viewvc?view=rev&revision=555276
This is why it's always been stated not to be bug compatible with other stacks. Please check the MIME specs and discuss in the mailing list before doing changes like this.
Referring to the comment on the above commit, angle brackets are actually required by the specs.
Following commit has added them back...
http://svn.apache.org/viewvc?view=rev&revision=573037
Unfortunately Axis2 1.3 release went out within this broken period :(...
On solution for James Chan, would be to 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: https://issues.apache.org/jira/browse/AXIS2-3196
> 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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
> 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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
>
> *******************************************************************************************************************************************************************
> RESPONSE HEADER viewed from TCPMON
> 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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <1....@apache.org>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3196) .NET C# using WSE 3.0 does not
interop with Axis2.0 Version 1.3
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thilina Gunarathne resolved AXIS2-3196.
---------------------------------------
Resolution: Fixed
Already fixed in the SVN.
> .NET C# using WSE 3.0 does not interop with Axis2.0 Version 1.3
> ---------------------------------------------------------------
>
> Key: AXIS2-3196
> URL: https://issues.apache.org/jira/browse/AXIS2-3196
> 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: 0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org
> 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 "<0....@apache.org>" and the start attribute is "0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org". 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.
>
> *******************************************************************************************************************************************************************
> RESPONSE HEADER viewed from TCPMON
> 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="0.urn:uuid:C77D473198EDDA58BB1189619919251@apache.org"; 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: <0....@apache.org>
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:MessageID>urn:uuid:C77D473198EDDA58BB1189619919249</wsa:MessageID><wsa:Action>urn:getMTOMAttachmentResponse</wsa:Action><wsa:RelatesTo>urn:uuid:52e3ff0c-6b3f-4555-82b7-fdf63054268d</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:getMTOMAttachmentResponse xmlns:ns1="http://SampleAxis2/xsd"><ns1:return><xop:Include href="cid:1.urn:uuid:C77D473198EDDA58BB1189619919252@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" /></ns1:return></ns1:getMTOMAttachmentResponse></soapenv:Body></soapenv:Envelope>
> 38
> --MIMEBoundaryurn_uuid_C77D473198EDDA58BB1189619919250
> c7
> Content-Type: text/plain
> Content-Transfer-Encoding: binary
> Content-ID: <1....@apache.org>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org