
| Key: |
JS2-232
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Ate Douma
|
| Reporter: |
Ate Douma
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
11/Apr/05 10:43 PM
|
|
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 refactoring.
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.
|
|
Description
|
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 refactoring.
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.
|
Show » |
| There are no subversion log entries for this issue yet.
|
|