Re: Invalid Content Type Field in the Mime Message

2007-04-26 Thread Jennifer Yang 

Thilina,

Here are the request and response.

Request:==
POST /broker/services/mm7 HTTP/1.0
Host: 127.0.0.1:
Content-Type: multipart/related;
boundary="NextPart_000_0125_01C19839.7237929064"; type=text/xml;
start=<0704191919160100>
Content-Length: 2215
SOAPAction: ""

--NextPart_000_0125_01C19839.7237929064
Content-Type: text/xml; charset="utf-8"
Content-ID: <0704191919160100>


http://schemas.xmlsoap.org/soap/envelope/";>

http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0";
env:mustUnderstand="1">
35556



http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0";>
   5.3.0
   209.86.124.29
   
3109108747



102

   
   
1177035556
Normal
jyy
   




--NextPart_000_0125_01C19839.7237929064
Content-Type: application/smil
Content-ID: <070419191900>

http://www.w3.org/2001/SMIL20/Language";>
  
   

 
 
   

 
 








 


--NextPart_000_0125_01C19839.7237929064
Content-Type: text/x-sktxt
Content-ID: <0704191919101100>


http://www.w3.org/1999/xhtml";>






  
   jyy
  



--NextPart_000_0125_01C19839.7237929064--

Response:==
HTTP/1.1 500 Internal Server Error
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_B2A7AB4D72019EFB341177619516424;
type="text/xml";
start="<0.urn:uuid:[EMAIL PROTECTED]>";charset=UTF-8
Date: Thu, 26 Apr 2007 20:31:56 GMT
Server: Apache-Coyote/1.1
Connection: close

--MIMEBoundaryurn_uuid_B2A7AB4D72019EFB341177619516424
content-type: text/xml; charset=UTF-8
content-transfer-encoding: 8bit
content-id: <0.urn:uuid:[EMAIL PROTECTED]>

http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing/noneurn:uuid:63FF5319E63FE7D3691177619516377http://www.w3.org/2005/08/addressing/soap/faultInvalid
Content Type Field in the Mime Message
--MIMEBoundaryurn_uuid_B2A7AB4D72019EFB341177619516424--


Do I need to register content types?  The log doesn't show which
content type that is invalid.  Wish the errors were more descriptive.
Is there more debug log I can turn on?

Thanks in advance,
--Jennifer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Invalid Content Type Field in the Mime Message

2007-04-26 Thread Thilina Gunarathne 

Please post the message snapshots to see what's going wrong...

You can use tcpmon[1] to capture the messages..

Thanks,
Thilina
[1]http://ws.apache.org/commons/tcpmon

On 4/26/07, Jennifer Yang <[EMAIL PROTECTED]> wrote:

Hi,

I'm integrating with a thirdparty client which sends two attachments.
I am getting the folllowing error:

2007-04-25 00:43:10,625 DEBUG
org.apache.axis2.transport.http.AxisServlet -
org.apache.axis2.AxisFault: Invalid Content Type Field in the Mi
me Message; nested exception is:
  org.apache.axiom.om.OMException: Invalid Content Type Field in
the Mime Message


I saw the following post, but didn't see any resolution.
http://marc.info/?l=axis-user&m=114707741728856&w=2

Any idea?

I wrote a test client that sends SWA that is similar to
samples\soapwithattachments.  However, I couldn't figure out how to
set the content type to try sending different type.

Thanks in advance,
Jennifer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]