You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2004/11/11 20:10:23 UTC
[jira] Created: (GERONIMO-476) jetty web app context could use interceptor based design
jetty web app context could use interceptor based design
--------------------------------------------------------
Key: GERONIMO-476
URL: http://nagoya.apache.org/jira/browse/GERONIMO-476
Project: Apache Geronimo
Type: Improvement
Versions: 1.0-M3
Reporter: David Jencks
Currently we have 2 jetty web app contexts related by inheritance: normal and +JACC. The normal one sets up the jndi component context and the transaction context for each handle call, and the jacc one also sets up the security context. All these functions are handled for ejbs by separate interceptors. A similar interceptor based design for jetty would be easier to understand and configure. With a final interceptor to call the correct jetty web app context method, the treatment of handle, start, and stop calls could probably also be fed through a single invoke method.
--
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
[jira] Closed: (GERONIMO-476) jetty web app context could use interceptor based design
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-476?page=history ]
David Jencks closed GERONIMO-476:
---------------------------------
Assign To: David Jencks
Resolution: Fixed
Fix Version: 1.0-M4
There is now only one web app context. Without a lot of cooperation from and refactoring of jetty, it's not possible to have an interceptor based design. However, I've faked it with a stack of "before/afters" that use an Object[] to store context during the call. This also made cross context dispatch work.
> jetty web app context could use interceptor based design
> --------------------------------------------------------
>
> Key: GERONIMO-476
> URL: http://issues.apache.org/jira/browse/GERONIMO-476
> Project: Geronimo
> Type: Improvement
> Components: web
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M4
>
> Currently we have 2 jetty web app contexts related by inheritance: normal and +JACC. The normal one sets up the jndi component context and the transaction context for each handle call, and the jacc one also sets up the security context. All these functions are handled for ejbs by separate interceptors. A similar interceptor based design for jetty would be easier to understand and configure. With a final interceptor to call the correct jetty web app context method, the treatment of handle, start, and stop calls could probably also be fed through a single invoke method.
--
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
[jira] Updated: (GERONIMO-476) jetty web app context could use interceptor based design
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-476?page=history ]
David Jencks updated GERONIMO-476:
----------------------------------
Component: web
> jetty web app context could use interceptor based design
> --------------------------------------------------------
>
> Key: GERONIMO-476
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-476
> Project: Apache Geronimo
> Type: Improvement
> Components: web
> Versions: 1.0-M3
> Reporter: David Jencks
>
> Currently we have 2 jetty web app contexts related by inheritance: normal and +JACC. The normal one sets up the jndi component context and the transaction context for each handle call, and the jacc one also sets up the security context. All these functions are handled for ejbs by separate interceptors. A similar interceptor based design for jetty would be easier to understand and configure. With a final interceptor to call the correct jetty web app context method, the treatment of handle, start, and stop calls could probably also be fed through a single invoke method.
--
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