geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-2478) ContextForwardServlet should have a registration mechanism
Date Wed, 01 Nov 2006 00:57:17 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2478?page=all ]

Aaron Mulder updated GERONIMO-2478:
-----------------------------------

    Description: 
Currently the ContextForwardServlet must be deployed separately for each URL path to redirect.

This does not work well for plugins, nor will it work well for a more fine-grained console
composed of multiple optional bits of functionality.

Instead, the ContextForwardServlet should listen on a single path (say, /portlet-resources)
and then have a registration mechanism that lets you add sub-mappings dynamically (/portlet-resources/foo/*
-> web app 1 and /portlet-resources/bar/* -> web app 2).  Presumably something where
it has a collection of GBeans and each web app that wants to register some forward with the
console deploys one or more instances of the GBean.

  was:
Currently the ContextForwardServlet must be deployed separately for each URL path to redirect.

This does not work well for plugins, nor will it work well for a more fine-grained console
composed of multiple optional bits of functionality.

Instead, the ContextForwardServlet should listen on a single path (say, /portlet-resources)
and then have a registration mechanism that lets you add sub-mappings dynamically (/portlet-resources/foo/*
-> web app 1 and /portlet-resources/bar/* -> web app 2).  Presumably something where
it has a collection of GBeans and each web app that wants to register some forward with the
console deploys one or more instances of the web app.


Fixed in 1.1.2 -- needs to be merged to 1.2

> ContextForwardServlet should have a registration mechanism
> ----------------------------------------------------------
>
>                 Key: GERONIMO-2478
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2478
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 1.1.1
>            Reporter: Aaron Mulder
>         Assigned To: Aaron Mulder
>             Fix For: 1.2, 1.1.2
>
>
> Currently the ContextForwardServlet must be deployed separately for each URL path to
redirect.
> This does not work well for plugins, nor will it work well for a more fine-grained console
composed of multiple optional bits of functionality.
> Instead, the ContextForwardServlet should listen on a single path (say, /portlet-resources)
and then have a registration mechanism that lets you add sub-mappings dynamically (/portlet-resources/foo/*
-> web app 1 and /portlet-resources/bar/* -> web app 2).  Presumably something where
it has a collection of GBeans and each web app that wants to register some forward with the
console deploys one or more instances of the GBean.

-- 
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

        

Mime
View raw message