Bug 794425 (JBEPP-1467)

Summary: The Portlet view in Application Registry does not refreshes when a Newer Version of a Portlet is deployed.
Product: [JBoss] JBoss Enterprise Portal Platform 6 Reporter: Anurag <adebnath>
Component: PortalAssignee: Default User <jbpapp-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: epp-bugs, nobody, theute
Target Milestone: ---   
Target Release: 6.0.x   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1467
Whiteboard: EPP_6_0_0_Candidate
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 794426 (view as bug list) Environment:
JBoss Enterprise Portal Platform 5.1 (GateIn Portal 3.1.0 )
Last Closed: 2012-09-03 11:39:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
hello1-portlet-0.0.1-SNAPSHOT-2.war
none
hello1-portlet-0.0.1-SNAPSHOT-1.war none

Description Anurag 2012-01-02 09:22:55 UTC
Complexity: Medium
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008U4nX&sfdc.override=1
Steps to Reproduce: Steps to reproduce.

1) Start JBoss Portal server .

2) Copy attached "hello1-portlet-0.0.1-SNAPSHOT.war" to the /deploy directory of JBoss Portal installation.
   Following can be seen in server console or the server.log -
   INFO  [TomcatDeployment] deploy, ctxPath=/hello1-portlet-0.0.1-SNAPSHOT

3) Go to Application Registry -> import applications
   Following log trace can be seen - 
   INFO  [ApplicationRegistryServiceImpl] Importing portlet (hello1-portlet-0.0.1-SNAPSHOT,local._hello1-portlet-0.0.1-SNAPSHOT.hello1-portlet) in categories [hello1-portlet-0.0.1-SNAPSHOT]

4) Create a Test Page and add the above portlet to the page.

5) Undeploy the above portlet from server(hello1-portlet-0.0.1-SNAPSHOT.war)
   From logs we can see - 
   INFO  [TomcatDeployment] undeploy, ctxPath=/hello1-portlet-0.0.1-SNAPSHOT
   WARN  [MainResourceResolver] Cannot find servlet context module

6) Deploy new portlet version (hello1-portlet-0.0.1-SNAPSHOT.war).  JBoss console shows - 
   INFO  [TomcatDeployment] deploy, ctxPath=/hello1-portlet

7) Go to Application Registry -> import applications
   INFO  [ApplicationRegistryServiceImpl] Importing portlet (hello1-portlet,local._hello1-portlet.hello1-portlet) in categories [hello1-portlet]

8) Go to Application Registry -> Category View . Newer portlet can be seen under Category "Hello1-Portlet"

9) Go to Application Registry -> Portlet View . The new portlet cannot be seen. The older version of portlet can be found under "hello1-portlet-0.0.1-SNAPSHOT"

10) Log out and Log back in. Now check the Portlet view. The newer version of the portlet can be seen and can now be added to any category and/or page.
Workaround Description: For now logging out and login back refreshes the Portlet view and then can be added to any desired category/page.
project_key: JBEPP

There are two versions of the same Portlet application. They have different context root.
I deploy the first portlet application, add it to a page. I then un-deploy the application and deploy newer version of its with a different context root (jboss-web.xml).

The Portlet View under the Application Registry does not shows the updated portlets when a newer version of a porltet is deployed.
The newer version of portlet application deploys properly. After doing an Import Application, new portlet can be see in the categories view, however, the Portlet view shows the older version of the portlet app.

When trying to add the new portlet from Portlet view ,to a category throws the error - 

ERROR [portal:UIPortalApplication] Error during the processAction phase
java.lang.IllegalArgumentException: Cannot create a content with a content id hello1-portlet/hello1-portlet with an existing different content id hello1-portlet-0.0.1-SNAPSHOT/hello1-portlet

Mentioning the steps to reproduce.

Comment 1 Anurag 2012-01-02 09:24:36 UTC
WAR files to reproduce the issue.

Comment 2 Anurag 2012-01-02 09:24:36 UTC
Attachment: Added: hello1-portlet-0.0.1-SNAPSHOT-2.war
Attachment: Added: hello1-portlet-0.0.1-SNAPSHOT-1.war


Comment 3 Anurag 2012-01-02 11:24:57 UTC
Link: Added: This issue is a dependency of GTNPORTAL-2319


Comment 4 hfnukal@redhat.com 2012-01-10 13:24:35 UTC
Labels: Removed: jboss portal Added: EPP_5_2_1_Candidate jboss portal


Comment 5 Thomas Heute 2012-01-13 15:24:44 UTC
Hot deployment is not a production feature.
This should not be a problem if server is restarted when a new version of the portlet is installed.

Comment 6 Thomas Heute 2012-01-13 15:24:56 UTC
Labels: Removed: EPP_5_2_1_Candidate jboss portal Added: EPP_6_0_0_Candidate


Comment 7 mark yarborough 2012-02-14 21:02:01 UTC
Workaround Description: Removed: 
For now logging out and login back refreshes the Portlet view and then can be added to any desired category/page. Added: For now logging out and login back refreshes the Portlet view and then can be added to any desired category/page.


Comment 8 Thomas Heute 2012-09-03 11:39:05 UTC

*** This bug has been marked as a duplicate of bug 794426 ***