[
http://jira.jboss.com/jira/browse/JBWS-1619?page=comments#action_12361301 ]
Thomas Diesler commented on JBWS-1619:
--------------------------------------
Wireshark output for "Use RequestDispatcher" shows that the cookie is available
as response header
The test passes.
POST /jaxrpc-jbws1619/TestEndpoint?datatype=JBossWSMessage HTTP/1.1
SOAPAction: ""
Content-Type: text/xml; charset=UTF-8
JBoss-Remoting-Version: 22
User-Agent: JBossRemoting - 2.2.0 SP2 (Bluto)
Host: 127.0.0.1:8080
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 250
<env:Envelope
xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:...
xmlns:ns1='http://org.jboss.test.ws/jbws1619'><String_1>Use
RequestDispatcher</String_1></ns1:echoString></env:Body></env:Envelope>HTTP/1.1
200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA
date=200705031018)/Tomcat-5.5
Set-Cookie: JSESSIONID=BEBF032F90D3CC7F3FF8936555A047AF; Path=/
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 03 May 2007 11:40:27 GMT
11e
<env:Envelope
xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:...
xmlns:ns1='http://org.jboss.test.ws/jbws1619'><result>httpSession:
BEBF032F90D3CC7F3FF8936555A047AF</result></ns1:echoStringResponse></env:Body></env:Envelope>
0
ServletEndpointContext.getHttpSession always creates HTTPSession
----------------------------------------------------------------
Key: JBWS-1619
URL:
http://jira.jboss.com/jira/browse/JBWS-1619
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Chris Laprun
Assigned To: Thomas Diesler
Priority: Minor
Fix For: jbossws-2.0.0
ServletEndpointContextImpl implements getHttpSession as simply request.getSession() which
results in always creating a session if one doesn't already exists.
ServletEndpointContext.getHttpSession javadoc specifies that null should be returned if no
session already exists. The implementation should probably be: request.getSession(false).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira