The following issue has been updated:

    Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
       Date: Sat, 17 Apr 2004 9:01 AM
    Changes:
             description changed from Environment: Weblogic 7, Win2k, Cactus 1.4.1

I have a ServletTestCase with two test methods - testLogin(), testLogout().
testlogin calls a doPost on a servlet which logs in user using HTTP request 
parameters, and places an object in session.
When I test assertNotNull for that session attribute, the test succeeds.

testlogout() calls another doPost which and logs the earlier user and 
invalidate the session. But when I do assertNotNull() for the same session 
attribute (before the actual call to servlet), the test fails..

I am using the same servlet...and session.isNew() always returns true 

This leads me to believe..
The HTTPSession created by testLogin() can nolonger be accessed by subsequent 
test method(s) ??

This is a bug..right ?? to Environment: Weblogic 7, Win2k, Cactus 1.4.1

I have a ServletTestCase with two test methods - testLogin(), testLogout().
testlogin calls a doPost on a servlet which logs in user using HTTP request 
parameters, and places an object in session.
When I test assertNotNull for that session attribute, the test succeeds.

testlogout() calls another doPost which and logs the earlier user and 
invalidate the session. But when I do assertNotNull() for the same session 
attribute (before the actual call to servlet), the test fails..

I am using the same servlet...and session.isNew() always returns true 

This leads me to believe..
The HTTPSession created by testLogin() can nolonger be accessed by subsequent 
test method(s) ??

This is a bug..right ??
             environment changed from Operating System: Windows NT/2K
Platform: PC to Operating System: Windows NT/2K
Platform: PC
             priority changed to Major
             Fix Version changed to 1.5-beta1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/CACTUS-30?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/CACTUS-30

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CACTUS-30
    Summary: Error accessing same http session across test methods
       Type: Bug

     Status: Reopened
   Priority: Major

    Project: Cactus
 Components: 
             Framework
   Fix Fors:
             1.5-beta1
   Versions:
             1.4.1

   Assignee: Vincent Massol
   Reporter: Avinash Chugh

    Created: Mon, 18 Nov 2002 4:50 PM
    Updated: Sat, 17 Apr 2004 9:01 AM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
Environment: Weblogic 7, Win2k, Cactus 1.4.1

I have a ServletTestCase with two test methods - testLogin(), testLogout().
testlogin calls a doPost on a servlet which logs in user using HTTP request 
parameters, and places an object in session.
When I test assertNotNull for that session attribute, the test succeeds.

testlogout() calls another doPost which and logs the earlier user and 
invalidate the session. But when I do assertNotNull() for the same session 
attribute (before the actual call to servlet), the test fails..

I am using the same servlet...and session.isNew() always returns true 

This leads me to believe..
The HTTPSession created by testLogin() can nolonger be accessed by subsequent 
test method(s) ??

This is a bug..right ??


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to