You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Stephane Nicoll (JIRA)" <ji...@apache.org> on 2007/06/04 21:10:26 UTC
[jira] Created: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
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
Priority: Critical
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.
[jira] Assigned: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger reassigned PLUTO-378:
------------------------------------
Assignee: Elliot Metsger
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-378:
---------------------------------
Fix Version/s: (was: 1.1.4)
This fix won't get into 1.1.4, and it may not get into the 1.1.x branch because its implementation may require changing interfaces which would break binary compatibility with past 1.1.x releases.
A thread has started on pluto-dev and is being fleshed out on general@ as to whether or not Pluto is the appropriate place for this code.
http://www.nabble.com/hot-deploy---auto-assembly-design-tf4041191.html
http://www.nabble.com/forum/ViewPost.jtp?post=11492057&framed=y
> 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
>
>
> 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.
[jira] Updated: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated PLUTO-378:
----------------------------
Assignee: (was: Ate Douma)
Assigned to myself and now unassigned again to be able to stop progress
> 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: Wish
> Components: portlet container
> Reporter: Stephane Nicoll
> Priority: Minor
> Fix For: 1.2.0
>
>
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Stephane Nicoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506065 ]
Stephane Nicoll commented on PLUTO-378:
---------------------------------------
Hey, anything new here? Let me know, I'll be glad to test.
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-378:
---------------------------------
Fix Version/s: 1.1.4
1.2.0
> 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.
[jira] Assigned: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma reassigned PLUTO-378:
-------------------------------
Assignee: Ate Douma (was: Elliot Metsger)
> 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: Wish
> Components: portlet container
> Reporter: Stephane Nicoll
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 1.2.0
>
>
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Stephane Nicoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501676 ]
Stephane Nicoll commented on PLUTO-378:
---------------------------------------
BTW, you should review your notification scheme. I don't receive notifications (neither by being the assignee nor by being in the watchers list).
Which is obviously annoying...
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Stephane Nicoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501671 ]
Stephane Nicoll commented on PLUTO-378:
---------------------------------------
OK. In practice, what should I do to enable/test this functionnality?
Thanks for your help.
> 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.
[jira] Updated: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated PLUTO-378:
----------------------------
Priority: Minor (was: Critical)
Affects Version/s: (was: 1.1.3)
Issue Type: Wish (was: Bug)
Downgrading this old issue to a Minor Wish.
*if* this is ever going to be provided for Pluto, then probably as a common functionality shared with Jetspeed-2 (which has this already).
There is nothing planned to do so though right now.
> 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: Wish
> Components: portlet container
> Reporter: Stephane Nicoll
> Assignee: Elliot Metsger
> Priority: Minor
> Fix For: 1.2.0
>
>
> 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.
[jira] Commented: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
Posted by "Stephane Nicoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503205 ]
Stephane Nicoll commented on PLUTO-378:
---------------------------------------
Someone should have a look to your notification scheme. I guess it's plugged to pluto-dev or something. I didn't received any notification so far.
Third option is good. At least, that's what I'm expecting.
> 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.