geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-488) jetty dispatch handling doesn't set component context, tx, or security properly in geronimo
Date Fri, 19 Nov 2004 06:46:33 GMT
jetty dispatch handling doesn't set component context, tx, or security properly in geronimo
-------------------------------------------------------------------------------------------

         Key: GERONIMO-488
         URL: http://nagoya.apache.org/jira/browse/GERONIMO-488
     Project: Apache Geronimo
        Type: Bug
  Components: web  
    Versions: 1.0-M3    
    Reporter: David Jencks
 Assigned to: David Jencks 


Currently we are setting the component jndi context, the thread context classloader, and the
security info per web app in the handle method of a web app context subclass.  This is wrong.
 This handle method is only called once from the socket listener.  Dispatches to other servlets,
in particular servlets in other web apps, do not go through this handle method again.  Therefore
the component context, transaction context, classloader, and security context are still those
of the first web app accessed.

The solution appears to be to remove this code from the handle method and put it in enterContextScope
and exitContextScope, public methods of Jetty's HttpContext.  These methods are called by
dispatchers when changing web apps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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


Mime
View raw message