[
https://jira.jboss.org/jira/browse/JBPORTAL-1894?page=com.atlassian.jira....
]
Hardy Massen commented on JBPORTAL-1894:
----------------------------------------
This behaviour also occurs in 2.7.2 and also if portlet-instances.xml is not used, i.e.
the instances are created manually via portal admin ui.
For now, undeployed instances are not listed in the portlet-instances view, though they
still exist in the table JBP_INSTANCE.
To me it's correct to not delete these instances in the table JBP_INSTANCE when
undeploying, so after re-deployment of the war-file they work again (makes only sense, if
portlet-instances.xml ist not used).
I would propose to grey out these undeployed instances in the portlet-instances view and
to give the possibility to delete them out of the DB by means of portlet-instances view.
So one may or may not delete them after undeployment.
Portlet instances cannot be deleted with the GUI after undeployment
-------------------------------------------------------------------
Key: JBPORTAL-1894
URL:
https://jira.jboss.org/jira/browse/JBPORTAL-1894
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Core Admin
Affects Versions: 2.6.3 Final
Reporter: Martin Putz
Assignee: Thomas Heute
When a portlet application (*.war) is undeployed, the portlet instances defined in
portlet-instances.xml remain in the JBP_INSTANCE table. This causes problems if the same
application is redeployed under a different context name.
The instances are also not listed in the management portlet GUI, which would allow to
delete them manually.
--
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