[
https://issues.apache.org/jira/browse/JS2-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538863
]
Scott T Weaver commented on JS2-799:
------------------------------------
I am going to make a slight addition to the API.
org.apache.jetspeed.tools.pamanager.PortletApplicationManagement will require
and additional startPortletApplication method that takes a specific context
path argument. This will have minimal effect on Jetspeed as a whole.
org.apache.jetspeed.tools.pamanager.PortletApplicationManager will require the
implemnetation of this method and
org.apache.jetspeed.container.JetspeedContainerServlet will need to call it.
If no "contextPath" init parameter has been defined for the
org.apache.jetspeed.container.JetspeedContainerServlet, it will use
"/"+contextName as the default which is basically what is happening at the
moment.
This will effect effect third party implementors who have written their own
implementations of PortletApplicationManagement. Fortunately, in most cases,
this is a very trivial task.
> 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]
