[
https://issues.apache.org/jira/browse/JS2-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538896
]
Scott T Weaver commented on JS2-799:
------------------------------------
Yes, the servlet checks to see if the "contextPath" was provided as init
parameter in the web.xml. If it was not, it will use "/"+contextName, which if
you look at the original startPortletApplication method, does the exact same
thing but within the method itself.
I don't think we ever fullu supported "/" for portlet apps and I am pretty sure
the contextPath started being ignored early on in the 2.0 development cycle.
This was fairly easy to get past as you could just change the entry in the
WEB_APPLICATION table to be "/". However, it appears now that this entry gets
reset every time the container starts up, at least it was for me.
> Jetspeed cannot deploy portlet applications that run from the "/" context.
> --------------------------------------------------------------------------
>
> Key: JS2-799
> URL: https://issues.apache.org/jira/browse/JS2-799
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 2.1
> Reporter: Scott T Weaver
> Assignee: Scott T Weaver
> Fix For: 2.1.3
>
>
> Jetspeed cannot deploy portlet applications that run from the "/" context.
> In fact it completely ignores the "contextPath" parameter in the
> JetspeedContainerServlet entry in the web.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
