Re: [jira] Closed: (GERONIMO-488) jetty dispatch handling doesn't set component context, tx, or security properly in geronimo

2004-12-13 Thread Manoj Purohit 
---BeginMessage---
Hi There,

I m on leave from 6th - 10th December.

Pls contact the following people during my absence.

1) StarHub PPTA/Telco Server Project - Seenu/Audrey
2) SIA VR - Chee Ming/Kevin
3) ICA ePassport Payment Module - Ivan or Kevin/Yew Kong
4) General presentation stuff - Kevin
 

---End Message---

[jira] Closed: (GERONIMO-488) jetty dispatch handling doesn't set component context, tx, or security properly in geronimo

2004-12-08 Thread David Jencks (JIRA) 
 [ http://nagoya.apache.org/jira/browse/GERONIMO-488?page=history ]
 
David Jencks closed GERONIMO-488:
-

 Resolution: Fixed
Fix Version: 1.0-M4

I've implemented an interceptor-like stack for these operations called from 
enterScope and leaveScope.

 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
 Assignee: David Jencks
  Fix For: 1.0-M4


 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