[
https://jira.jboss.org/jira/browse/JBPORTAL-2202?page=com.atlassian.jira....
]
Thomas Heute resolved JBPORTAL-2202.
------------------------------------
Resolution: Won't Fix
The portlet is references by either using the context path or the app-name if any.
If you have an app-name defined, the portlet won't be reference anymore so you would
need to recreate a new window for that new reference and delete the former one for
cleanup.
Cannot Change Portlet app-name for a Portlet Instance
-----------------------------------------------------
Key: JBPORTAL-2202
URL:
https://jira.jboss.org/jira/browse/JBPORTAL-2202
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.7.0 CR1
Environment: Bundled portal/as: jboss-portal-2.7.0.CR1-bundled.zip on WinXP.
Reporter: Robert R
Working with the Maven richfaces-basic archetype, it creates the richfaces-basic.war
which uses the app-name "richfacesEchoApp" inside jboss-app.xml. If you later
try changing the app-name and redeploying, the portlet no longer appears.
I finally found the text "richfacesEchoApp" in the hypersonic script found
here:
jboss-portal-2.7.0.CR1\server\default\data\portal\hypersonic\database.script
Here is a sample line:
INSERT INTO JBP_INSTANCE
VALUES(21,'RichfacesEchoPortletInstance','local.richfacesEchoApp.RichfacesEchoPortlet',FALSE,NULL)
Right now - in order to change the app-name (as a workaround) - you need to do one of the
following:
1. Update the hypersonic script
2. Delete the jboss-portal-2.7.0.CR1\server\default\data\portal\hypersonic\ directory,
or
3. Also change the name of the portlet instance so that it gets its own record
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira