Re: Axis 2.0 Content-type

2007-10-03 Thread keith chapman
OTECTED]> wrote: > > > > > > Hi Keith > > > > Wonder if you had a chance to look at this. > > > > Thanks > > Chandru Ganesan > > > > > > ------------------ > > *From:* Ganesan, Chandru > > *Sent:* Tues

RE: Axis 2.0 Content-type

2007-10-03 Thread Ganesan, Chandru
an, Chandru Sent: Tuesday, October 02, 2007 1:11 PM To: axis-user@ws.apache.org Subject: RE: Axis 2.0 C

Re: Axis 2.0 Content-type

2007-10-03 Thread keith chapman
o look at this. > > Thanks > Chandru Ganesan > > > -- > *From:* Ganesan, Chandru > *Sent:* Tuesday, October 02, 2007 1:11 PM > *To:* axis-user@ws.apache.org > *Subject:* RE: Axis 2.0 Content-type > > *-* <http://localhost:7001/axis2/re

RE: Axis 2.0 Content-type

2007-10-03 Thread Ganesan, Chandru
Hi Keith Wonder if you had a chance to look at this. Thanks Chandru Ganesan From: Ganesan, Chandru Sent: Tuesday, October 02, 2007 1:11 PM To: axis-user@ws.apache.org Subject: RE: Axis 2.0 Content-type

RE: Axis 2.0 Content-type

2007-10-02 Thread Ganesan, Chandru
Sent: Tuesday, October 02, 2007 12:48 PM To: axis-user@ws.apache.org Subject: Re: Axis 2.0 Content-type This is strange cause Axis actually treated your request as SOAP 1.1 cause the response itself is soap 1.1 but with the wrong content-type header. May i k

Re: Axis 2.0 Content-type

2007-10-02 Thread keith chapman
quot;e" > 117515 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.content- << > "8" > 117515 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.content- << > "[\r]" > 117515 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wi

RE: Axis 2.0 Content-type

2007-10-02 Thread Ganesan, Chandru
on.A.J ] httpclient.wire.content - << "e" 117515 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.content - << "8" 117515 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.content - << "[\r]" 117515 DEBUG [ class ro.sync.ui.applicati

Re: Axis 2.0 Content-type

2007-10-02 Thread keith chapman
neither matches, the SOAP client throws the error message you received. > > Thanks > Chandru Ganesan > > > ------------------ > *From:* keith chapman [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, October 02, 2007 11:30 AM > *To:* axis-user@ws.apache.org >

Re: Axis 2.0 Content-type

2007-10-02 Thread keith chapman
as > "application/soap+xml" in which case it considers the response to be of > version 1.2. > > As neither matches, the SOAP client throws the error message you received. > > Thanks > Chandru Ganesan > > > ------------------ > *From:* kei

RE: Axis 2.0 Content-type

2007-10-02 Thread Ganesan, Chandru
__ From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 11:30 AM To: axis-user@ws.apache.org Subject: Re: Axis 2.0 Content-type Hi, The SOAPaction is an attribute which can be used to dispatch a me

Re: Axis 2.0 Content-type

2007-10-02 Thread keith chapman
appreciate your thoughts on it. > > Thanks > Chandru Ganesan > > > -- > *From:* keith chapman [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, October 02, 2007 10:59 AM > *To:* axis-user@ws.apache.org > *Subject:* Re: Axis 2.0 Content-type > > No you dont need to modify y

RE: Axis 2.0 Content-type

2007-10-02 Thread Ganesan, Chandru
thoughts on it. Thanks Chandru Ganesan From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 10:59 AM To: axis-user@ws.apache.org Subject: Re: Axis 2.0 Content-type No you dont need

Re: Axis 2.0 Content-type

2007-10-02 Thread keith chapman
No you dont need to modify your axis2.xml leave it as it was. Can you check the SOAP request you sent. I'm sure it does not contain the SOAPAction header. In SOAP 1.1 the SOAPAction is mandatory and axis2 uses this as a key to differentiate between REST request and SOAP 1.1 request (As some REST r