You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <ji...@apache.org> on 2006/10/31 18:02:17 UTC
[jira] Assigned: (GERONIMO-2478) ContextForwardServlet should have
a registration mechanism
[ http://issues.apache.org/jira/browse/GERONIMO-2478?page=all ]
Aaron Mulder reassigned GERONIMO-2478:
--------------------------------------
Assignee: Aaron Mulder
> 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 web app.
--
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