Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 50850 invoked from network); 2 Oct 2007 16:30:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Oct 2007 16:30:14 -0000 Received: (qmail 51178 invoked by uid 500); 2 Oct 2007 16:29:57 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 50351 invoked by uid 500); 2 Oct 2007 16:29:55 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 50340 invoked by uid 99); 2 Oct 2007 16:29:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2007 09:29:55 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of keithgchapman@gmail.com designates 72.14.214.233 as permitted sender) Received: from [72.14.214.233] (HELO hu-out-0506.google.com) (72.14.214.233) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2007 16:29:54 +0000 Received: by hu-out-0506.google.com with SMTP id 23so2006256huc for ; Tue, 02 Oct 2007 09:29:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=xFCHrrYiRXTm9ktKJzZafkhy6ba8lEgZsy2/AGgDLL8=; b=d//3V2Epci7UZvbyZAGyAwuuFA6DOLpKnBjps5QhJFI3xUA8R8UmEc67kZLIoYzBWjdToP4NAPxZvd6qfLvKv/wObJjzuIy+ArAAOMZPeOqRLx1AkmHvMPy9Nr21vhx6pPoA6fZcN/6zOmU1hYYlPgNTKL9NOEr8sFE2T6dtNDA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=mWE3mMh0To9sKb81XCLvRnsjtwuLI8vyyD6RDBoe0T10NZjEN5wIcAL/hCx8bKqE3rUohYzkTr97zbr1CQ/I4Od/ZWOQ/EeesJ2uEIqO1jaJRXDBTqnnzBlem6JQ4VsVnqml1HQb974ZIr9TLrIb0PQ4OXAYUp+kU5ke3NxAV0Q= Received: by 10.142.90.8 with SMTP id n8mr76243wfb.1191342570585; Tue, 02 Oct 2007 09:29:30 -0700 (PDT) Received: by 10.141.63.18 with HTTP; Tue, 2 Oct 2007 09:29:30 -0700 (PDT) Message-ID: Date: Tue, 2 Oct 2007 21:59:30 +0530 From: "keith chapman" To: axis-user@ws.apache.org Subject: Re: Axis 2.0 Content-type In-Reply-To: <9B85F3094DA8AB4AB6E3CE743A5698B902133CEE@G3W0071.americas.hpqcorp.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6677_24596963.1191342570576" References: <9B85F3094DA8AB4AB6E3CE743A5698B902133B6A@G3W0071.americas.hpqcorp.net> <9B85F3094DA8AB4AB6E3CE743A5698B902133CEE@G3W0071.americas.hpqcorp.net> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_6677_24596963.1191342570576 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, The SOAPaction is an attribute which can be used to dispatch a message. If a service advertises that it uses a SOAPAction you can set it in the client so that the client sends it in the request. As SOAPaction is mandatory in SOAP 1.1 request you should atleast have the following header SOAPAction: "" What is the client that your using. If its axis2 it does the above (Add an empty SOAPaction if its not specified) if the request is SOAP 1.1. Thanks, Keith On 10/2/07, Ganesan, Chandru wrote: > > > Hi Keith > > Thanks for the quick response. > > As you've guessed correctly the request does not contain a SOAPAction. I'm > not quite clear about what should the value of SOAPAction be so that Axis > 2.0 treats it as SOAP 1.1 request. As I'm researching this topic, > appreciate your thoughts on it. > > Thanks > Chandru Ganesan > > > ------------------------------ > *From:* keith chapman [mailto:keithgchapman@gmail.com] > *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 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 request uses text/xml as the contentType). The reason your response > was application/xml is because Axis2 treated your request as a REST request > and responded accordingly. > > Thanks, > Keith. > > On 10/2/07, Ganesan, Chandru wrote: > > > > > > Hi > > > > When I send a SOAP request to Axis 2.0 service the response contains > > content-type=application/xml in the HTTP header. This causes WSDL/SOAP > > client tool to throw an exception as it doesn't understand the > > content-type of application/xml. For SOAP 1.1 it expects > > content-type=text/xml. I modified the Axis2.xml to include following > > lines. But this still doesn't return content-type=text/xml. Am I > > missing something in the Axis2.xml so that content-type of text/xml can > > be returned in the response. > > > > Appreciate your input very much. > > > > Modified Axis2.xml contains following lines for text/xml: > > ========================================================= > > > > > class=""/> > > > class=""/> > > > class=""/> > > > > > > > > SOAP response > > ============= > > "HTTP/1.1 200 OK[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Via: 1.1 HOUWEBPROXY03[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Connection: Keep-Alive[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Proxy-Connection: Keep-Alive[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Transfer-Encoding: chunked[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Date: Mon, 01 Oct 2007 19:37:41 GMT[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Content-Type: application/xml; charset=utf-8[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Cache-Control: no-cache="set-cookie"[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "Set-Cookie: > > JSESSIONID=zLGnHBMF7LRLqfr59qZ8TGWQXyHx6j7qh1BBTZyGQRXjsZn3Wb9n!16440382 > > 36; path=/[\r][\n]" > > 128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header > > - << "X-Powered-By: Servlet/2.4 JSP/2.0[\r][\n]" > > > > > > thanks > > Chandru Ganesan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ ------=_Part_6677_24596963.1191342570576 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,

The SOAPaction is an attribute which can be used to dispatch a message. If a service advertises that it uses a SOAPAction you can set it in the client so that the client sends it in the request. As SOAPaction is mandatory in SOAP 1.1 request you should atleast have the following header

SOAPAction: ""

What is the client that your using. If its axis2 it does the above (Add an empty SOAPaction if its not specified) if the request is SOAP 1.1.

Thanks,
Keith

On 10/2/07, Ganesan, Chandru <chandru.ganesan@hp.com> wrote:
 
Hi Keith
 
Thanks for the quick response.
 
As you've guessed correctly the request does not contain a SOAPAction. I'm not quite clear about what should the value of SOAPAction be so that Axis 2.0 treats it as SOAP 1.1 request. As I'm researching this topic, appreciate your thoughts on it.

Thanks
Chandru Ganesan

 

From: keith chapman [mailto:keithgchapman@gmail.com]
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 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 request uses  text/xml as the contentType). The reason your response was application/xml is because Axis2 treated  your request as a REST request and responded accordingly.

Thanks,
Keith.

On 10/2/07, Ganesan, Chandru <chandru.ganesan@hp.com> wrote:

Hi

When I send a SOAP request to Axis 2.0 service the response contains
content-type=application/xml in the HTTP header. This causes WSDL/SOAP
client tool to throw an exception as it doesn't understand the
content-type of application/xml. For SOAP 1.1 it expects
content-type=text/xml. I  modified the Axis2.xml to include following
lines. But this still doesn't return  content-type=text/xml. Am I
missing something in the Axis2.xml so that content-type of text/xml can
be returned in the response.

Appreciate your input very much.

Modified Axis2.xml contains following lines for text/xml:
=========================================================
<messageBuilders>
<messageBuilder contentType="text/xml"
class=""/>
<messageBuilder contentType=""
class=""/>
<messageBuilder contentType="multipart/form-data"
class=""/>
</messageBuilders>


SOAP response
=============
"HTTP/1.1 200 OK[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Via: 1.1 HOUWEBPROXY03[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Connection: Keep-Alive[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Proxy-Connection: Keep-Alive[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Transfer-Encoding: chunked[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Date: Mon, 01 Oct 2007 19:37:41 GMT[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Content-Type: application/xml; charset=utf-8[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Cache-Control: no-cache="set-cookie"[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "Set-Cookie:
JSESSIONID=zLGnHBMF7LRLqfr59qZ8TGWQXyHx6j7qh1BBTZyGQRXjsZn3Wb9n!16440382
36; path=/[\r][\n]"
128708 DEBUG [ class ro.sync.ui.application.A.J ] httpclient.wire.header
- << "X-Powered-By: Servlet/2.4 JSP/2.0[\r][\n]"


thanks
Chandru Ganesan

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org




--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/



--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/ ------=_Part_6677_24596963.1191342570576--