portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@jakarta.apache.org>
Subject [jira] Closed: (JS2-232) Invalid contextPath value returned to local portlet applications / decorators
Date Mon, 11 Apr 2005 13:47:19 GMT
     [ http://issues.apache.org/jira/browse/JS2-232?page=history ]
Ate Douma closed JS2-232:

    Resolution: Fixed

> Invalid contextPath value returned to local portlet applications / decorators
> -----------------------------------------------------------------------------
>          Key: JS2-232
>          URL: http://issues.apache.org/jira/browse/JS2-232
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Container
>     Versions: 2.0-M2
>     Reporter: Ate Douma
>     Assignee: Ate Douma
>      Fix For: 2.0-M3

> The web application definition contextRoot of local portlet applications was changed
from /jetspeed to <portal> (which is not a valid contextPath of course) during the deployment
> Because their contextRoot no longer is hardcoded, it allows changing the contextPath
of the portal itself (even after deployment), but it also cannot be used anymore as a real
contextPath (for non-local Portlet Applications it still can).
> The current o.a.j.engine.servlet.ServletRequestImpl still uses this attribute for implementation
of the getContextPath() method, resulting in an invalid value (<portal>) for the local
portlet applications, e.g. the layout portlets and decorators.

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:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message