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 "Craig Doremus (JIRA)" <pl...@jakarta.apache.org> on 2005/01/30 15:49:17 UTC
[jira] Created: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Administrative interface for deploying portlets to Pluto
--------------------------------------------------------
Key: PLUTO-103
URL: http://issues.apache.org/jira/browse/PLUTO-103
Project: Pluto
Type: New Feature
Components: portal driver
Versions: 1.0.1-rc1, 1.0.1-rc2
Environment: All environments
Reporter: Craig Doremus
Attachments: pluto-admin-portlet-v0.5-01-29-2005.zip
We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "David DeWolf (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=comments#action_58886 ]
David DeWolf commented on PLUTO-103:
------------------------------------
Craig,
This is GREAT! Thanks for your efforts. Would you be able to do me one favor before I commit this. Is it possible for you to convert your ant build into a maven build modeled after the testsuite build. By doing so, we can maintain consistency and add this portlet as a subproject within the maven system.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
Craig Doremus updated PLUTO-103:
--------------------------------
Attachment: Readme.txt
DeployWarHelp.html
A small correction is added to these files. The DeployWarHelp.html file goes in the webapps/jsp directory of the source distribution.
This correction states that deployment using the Deploy War portlet only requires a valid war file. No preprocessing by the deployment environment or maven is required.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
Craig Doremus updated PLUTO-103:
--------------------------------
Attachment: PlutoAdmin0.5Screenshot.jpg
Screenshot of the Pluto Admin Portlet Application 'home page'.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Attachments: PlutoAdmin0.5Screenshot.jpg, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
Craig Doremus updated PLUTO-103:
--------------------------------
Attachment: adminportletapp.zip
adminportletapp-svnchanges.zip
I have added a maven script (maven.xml, project.xml and project.properties) to this distribution, bundled in the adminportletapp.zip file. I've also added Apache 2.0 license headers throughout. The adminportletapp-svnchanges.zip file includes files that need to be updated in Pluto's SVN repository to accomodate the portlet application into the binary distribution of Pluto. This version removed the necessity for setting tomcat-home in pluto-admin.properties for the proper functioning of the webapp. See the Readme files in each archive for details.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Priority: Minor
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, adminportletapp-svnchanges.zip, adminportletapp.zip, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
Craig Doremus updated PLUTO-103:
--------------------------------
Attachment: pluto-admin-portlet-v0.5-01-29-2005.zip
This is the source distribution of our portlet application. See the Readme.txt file for details.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Attachments: pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "David DeWolf (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
David DeWolf updated PLUTO-103:
-------------------------------
Priority: Minor (was: Major)
Setting to minor simply because it is an enhancement
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Priority: Minor
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "David DeWolf (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=history ]
David DeWolf resolved PLUTO-103:
--------------------------------
Resolution: Fixed
Fix Version: 1.0.1-rc3
Committed with a few modifications.
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Priority: Minor
> Fix For: 1.0.1-rc3
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, adminportletapp-svnchanges.zip, adminportletapp.zip, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-103) Administrative interface for deploying portlets to Pluto
Posted by "David DeWolf (JIRA)" <pl...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-103?page=comments#action_59381 ]
David DeWolf commented on PLUTO-103:
------------------------------------
I have made significant progress in preparing these portlets for checkin, but still have some work to do. They look very cool and I think they are a great addition to the community, however, before I check them in I'd like to get past some of the errors I'm having.
So far, these are the modifications I've made:
- Removed the Ant Script to reduce maintence and
duplication of dependencies.
- Removed log4j Dependency
- Updated Castor dependency to match portal version
- Added Admin Portlet Deployment to fullDeployment goal
Right now, I'm getting errors in the Entity ang Page registry portlets:
1) If I use seperate CATALINA_BASE and CATALINA_HOME directories. This isn't a real big show stopper in my mind. It should be fixed eventually, but it won't prevent me from checking it in.
2) Because the portlet webapp does not have access to the portalImpl classes upon which it depends. I don't really want to pull these classes out of the portal app and put them in the common or shared dirs. IMHO we allready have too many of those - yuk! The other option we have is to support a second approach to portlet-app deployments - once which allows portlets to be deployed within the portal app itself. This approach would allow the admin portlets to have access to the portlets. The other possibility of course is to duplicate the classes - but I'm not a big fan of duplication.
I will continue to work through these and hopefully check them in soon. If anyone has any ideas about #2, please share :)
> Administrative interface for deploying portlets to Pluto
> --------------------------------------------------------
>
> Key: PLUTO-103
> URL: http://issues.apache.org/jira/browse/PLUTO-103
> Project: Pluto
> Type: New Feature
> Components: portal driver
> Versions: 1.0.1-rc1, 1.0.1-rc2
> Environment: All environments
> Reporter: Craig Doremus
> Priority: Minor
> Attachments: DeployWarHelp.html, PlutoAdmin0.5Screenshot.jpg, Readme.txt, adminportletapp-svnchanges.zip, adminportletapp.zip, pluto-admin-portlet-v0.5-01-29-2005.zip
>
> We have created a portlet application that is an administrative interface to Pluto 1.0.1. These portlets do all the work of unzipping the portlet application's war file in its proper place and updating the two Pluto registries (portletentityregistry.xml and pageregistry.xml) and portletcontexts.txt to fully deploy a custom portlet to Pluto (RC1 or RC2).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira