[ http://issues.apache.org/jira/browse/JS2-364?page=all ]
Ate Douma resolved JS2-364:
---------------------------
Resolution: Won't Fix
It turns out to be rather difficult to "know" under which context the portal is
running when you're not invoked from a servlet request.
As the DeployPortletAppEventListener is running in its own thread, and can
invoke a deployment when not one request has been send of to the portal,
this becomes very difficult to handle automatically.
And then, what if the war contains a context.xml (Tomcat) redefining its
context? Should we start checking that too?
And finally, a user can also accidentally drop a war directly in the (Tomcat)
webapps folder, certainly leading to disaster.
In short, I don't think this can really be handled/fixed 100%.
Furthermore, in my opinion, this is a user error which hardly will ever occur
and certainly not twice by the same user for sure ;-)
So, I'm going to classify this issue as "Won't Fix" for now.
If anyone thinks differently, then just reopen it again.
> Check for deploying Portlet Apps with same name as portal
> ---------------------------------------------------------
>
> Key: JS2-364
> URL: http://issues.apache.org/jira/browse/JS2-364
> Project: Jetspeed 2
> Type: Bug
> Components: Deployment
> Versions: 2.0-M4
> Reporter: David Sean Taylor
> Assignee: Ate Douma
> Fix For: 2.0-FINAL
>
> If you have a Jetspeed portal with the context /jetspeed, and you drop in a
> portlet application into the deploy directory with the name /jetspeed, then
> Jetspeed will blindly install the portlet app over itself.
> This bug occurs with all portal names.
> We need to check for this exception, and disallow this special case.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
