You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sebastian Szczygiel <se...@openknowledge.de> on 2006/05/08 10:36:14 UTC
[Axis2] Invalid Content Type Field in the Mime Message while sending MTOM message
Hi,
I wrote a client which sends a SOAP message with MTOM attachment. The
only response I get from the server is
"Invalid Content Type Field in the Mime Message"
Here's the request catched with tcpmon:
POST /dentiv-hkp/services/dentiv-hkp_1_0 HTTP/1.1
User-Agent: Axis/2.0
Host: localhost:8081
Transfer-Encoding: chunked
Content-Type: multipart/related;
boundary=MIMEBoundaryurn:uuid:79B88131D7E2B52CE411470755667501;
type="application/xop+xml";
start="<0....@apache.org>";
start-info="application/soap+xml"; charset=UTF-8;action="""";
907
--MIMEBoundaryurn:uuid:79B88131D7E2B52CE411470755667501
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"><soapenv:Header
/><soapenv:Body
..
<api:attachments>
<api:attachment>
<attachment-id>1</attachment-id>
<attachment-name>test-data</attachment-name>
<attachment-type-version>1</attachment-type-version>
<attachment-data><xop:Include
href="cid:1.urn:uuid:79B88131D7E2B52CE411470755667653@apache.org"
xmlns:xop="http://www.w3.org/2004/08/xop/include" /></attachment-data>
</api:attachment>
</api:attachments>
...
</soapenv:Body></soapenv:Envelope>
--MIMEBoundaryurn:uuid:79B88131D7E2B52CE411470755667501
content-type: text/plain
content-transfer-encoding: binary
content-id: <1....@apache.org>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
...
</soapenv:Body>
</soapenv:Envelope>
3b
--MIMEBoundaryurn:uuid:79B88131D7E2B52CE411470755667501--
0
[Axis2] Build Failure in Axis2
Posted by Eran Chinthaka <ch...@opensource.lk>.
Hi all,
Do you all experience a compile failure in Axis2. I have some local
changes, but that doesn't seem to affect this problem.
The problem is in the jaxbri module. Is it because I'm in jdk 1.5 I get
this problem ?
Just wanted to know whether others also getting the same error.
Chinthaka