[
https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501618
]
Craig Doremus commented on PLUTO-378:
-------------------------------------
The file upload and deployment capabilities in Pluto 1.0.1 seem to be what you
are looking for in the Pluto 1.1+ line. Last year, I worked on a way to do
this. Here is an outline of my approach:
1. Upload portlet war file to a temp directory.
2. Unzip the war
3. Modify the web.xml file to add the PortletServlet records
4. Re-archive the war file
5. Move the newly instrumented war file to the Tomcat's deployment directory
6. Create and deploy a Tomcat-specific context XML file (unless there is one
within META-INF of the war file)
Pluto would need to be restarted to pick up the newly deployed portlet war or a
hot-deployment mechanism would need to be added to this list. Also note that
steps 5 and 6 are Tomcat specific, so some sort of configuration should be
added via Spring to allow a portlet deployment scheme to be adapted if Pluto is
deployed in another app servers.
My work, which is the 1.1.0-ADMIN-PORTLET-CRAIG SVN branch, is concentrated in
the org.apach.pluto.driver.services.portal.admin.impl package of the
pluto-portal-driver module. FYI, this code is available, as is my assistance on
this issue.
> 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.
