Transport session doesn't work for in-only operations
-----------------------------------------------------

                 Key: AXIS2-4711
                 URL: https://issues.apache.org/jira/browse/AXIS2-4711
             Project: Axis2
          Issue Type: Bug
          Components: transports
         Environment: Ubuntu 9.10
JDK 1.6

            Reporter: chamara silva
            Priority: Critical


i have used in-only axis2 service and in response for the first request contain 
JSESSIONID.but second request does not include JSESSIONID.

First Request - 

POST /services/MSSQL_DataService.SOAP11Endpoint/ HTTP/1.1

Content-Type: application/soap+xml; charset=UTF-8; action="urn:begin_boxcar"

User-Agent: Axis2

Host: 127.0.0.1:9764

Transfer-Encoding: chunked



93

<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
      <soapenv:Body />
   </soapenv:Envelope>0




First Response - 

HTTP/1.1 202 Accepted

Server: Apache-Coyote/1.1

Set-Cookie: JSESSIONID=3C156A6E6257C94446638BDACF01346D; Path=/

Content-Type: text/xml;charset=UTF-8

Transfer-Encoding: chunked

Date: Wed, 12 May 2010 09:58:51 GMT



0



Second Request - 

POST /services/MSSQL_DataService.SOAP11Endpoint/ HTTP/1.1

Content-Type: application/soap+xml; charset=UTF-8; action="urn:op_insertquery"

User-Agent: Axis2

Host: 127.0.0.1:9764

Transfer-Encoding: chunked



121

<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
      <soapenv:Body>
         <ns1:op_insertquery xmlns:ns1="http://ws.wso2.org/dataservice";>
            <ns1:name>ZZZZ</ns1:name>
            <ns1:age>1</ns1:age>
         </ns1:op_insertquery>
      </soapenv:Body>
   </soapenv:Envelope>0




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to