geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Closed: (GERONIMO-476) jetty web app context could use interceptor based design
Date Mon, 07 Mar 2005 00:44:52 GMT
     [ ]
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:
>      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:
If you want more information on JIRA, or have a bug to report see:

View raw message