[
https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502004
]
Elliot Metsger commented on PLUTO-378:
--------------------------------------
so this could be a list conversation but its here for stephane's benefit
(providing notifications are working - they work for me....)
There are a few approaches:
1) admin portlet providing users or admins the ability to assemble and deploy
the war - as craig alludes to there is some code in a branch for this
2) maven plugin which assembles portlet at package time. of course the
packaged war is assembled specifically for the pluto container. this exists
now in 1.1.x. http://portals.apache.org/pluto/v11/deploying.html
a third option is hot deployment - a user/admin actually places an unassembled
war in a specific directory of the application server and it is automatically
assembled and registered with the portlet container. Hot deploy should be
pretty easy to add. we already have auto-registration, so we should just have
to add the hot-deploy code, and then stephane can just plop the (unassembled)
war in a directory and have pluto pick it up, assemble, and deploy it.
> Pluto requires custom entries in web.xml whcih prevents the deployment of JSR
> 168 portlest
> ------------------------------------------------------------------------------------------
>
> Key: PLUTO-378
> URL: https://issues.apache.org/jira/browse/PLUTO-378
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 1.1.3
> Reporter: Stephane Nicoll
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.2.0, 1.1.4
>
>
> According to the documentation, pluto requires any war containing portlets to
> be updated by a plugin in order to allow a deployment in pluto, see
> http://portals.apache.org/pluto/v11/deploying.html
> This is a show stopper for people working with several portlets container
> since the stuff that needs to be added makes a deployment into another portal
> system impossible. Pluto should inject the necessary stuff on the fly instead
> (just like Liferay does for instance).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
