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-userm=114707741728856w=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]

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

?xml version=1.0 encoding=utf-8 ?
env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/;
env:Header
mm7:TransactionID
xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0;
env:mustUnderstand=1
35556
/mm7:TransactionID
/env:Header
env:Body
DeliverReq 
xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0;
   MM7Version5.3.0/MM7Version
   MMSRelayServerID209.86.124.29/MMSRelayServerID
   Sender
Number3109108747/Number
/Sender
Recipients
To
ShortCode102/ShortCode
/To
   /Recipients
   LinkedID/LinkedID
TimeStamp1177035556/TimeStamp
PriorityNormal/Priority
Subjectjyy/Subject
   Content href=cid:070419191900/
/DeliverReq
/env:Body
/env:Envelope

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

smil xmlns=http://www.w3.org/2001/SMIL20/Language;
  head
   meta name=mms_skt_version content=4.0 /
layout
 root-layout background-color=#FF width=220 height=198 
/
 region id=text1 top=0 left=0 width=220 height=198
z-index=0 fit=hidden /
   /layout

 /head
 body
par repeatCount=indefinite 


text id=mc_textId repeatCount=indefinite 
region=text1
src=0704191919101100  begin=0 dur=10 
param name=style value=normal valuetype=data 
/param
/text
/par
 /body
/smil

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

?xml version=2.0 encoding=ksc5601?
xt xmlns=http://www.w3.org/1999/xhtml;
head
style type =text/css
!--
   color1{color:  0,   1,   0;}

 --
/style
/head
body bgcolor=#FF
  div
   color1jyy/color1
  /div
/body
/xt

--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]

?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:wsa=http://www.w3.org/2005/08/addressing;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Headerwsa:ReplyTowsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address/wsa:ReplyTowsa:MessageIDurn:uuid:63FF5319E63FE7D3691177619516377/wsa:MessageIDwsa:Actionhttp://www.w3.org/2005/08/addressing/soap/fault/wsa:Action/soapenv:Headersoapenv:Bodysoapenv:Faultfaultcode/faultcodefaultstringInvalid
Content Type Field in the Mime Message/faultstringdetail
//soapenv:Fault/soapenv:Body/soapenv:Envelope
--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]