[jira] Closed: (GERONIMO-474) jetty web app context could use interceptor based design

["David Jencks (JIRA)" <de...@geronimo.apache.org>]

     [ http://issues.apache.org/jira/browse/GERONIMO-474?page=all ]
     
David Jencks closed GERONIMO-474:
---------------------------------

    Fix Version: 1.0-M4
                 1.0-M5
     Resolution: Fixed
      Assign To: David Jencks

This was implemented months ago, although I had to use a "before/after" design rather than true interceptors.  Perhaps a future version of jetty will allow an interceptor based design.

> jetty web app context could use interceptor based design
> --------------------------------------------------------
>
>          Key: GERONIMO-474
>          URL: http://issues.apache.org/jira/browse/GERONIMO-474
>      Project: Geronimo
>         Type: Improvement
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M4, 1.0-M5

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira