Bug 805288

Summary: refresh need when deleting page in portal configured using JTA
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: vramik
Component: PortalAssignee: mposolda
Status: ASSIGNED --- QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.2.1.ER02, 5.2.1.ER03CC: epp-bugs, mposolda
Target Milestone: ---   
Target Release: 5.2.x   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description vramik 2012-03-20 19:50:57 UTC
Description of problem:
When you delete page in portal configured using JTA the page has to be refreshed (or click e.g. quick search icon) to not see deleted page.

How reproducible:
Start portal according to configuration of this job: 
https://hudson.qa.jboss.com/hudson/job/epp5_ui_selenium_tests_db_mysql5.5_JTA/

Steps to Reproduce:
1. Open portal and sign in as a root
2. go to page management
3. click delete icon of any page
4. Click OK
5. page is still displayed
 
Additional info: 
I tried this manually using mysql5.5 with no-tx datasource and it works fine.

Comment 1 mposolda 2012-06-27 11:25:52 UTC
This behaviour is caused by eXo JCR behaviour, which I described here https://jira.exoplatform.org/browse/JCR-1804 . I will wait for response from JCR team.

Fact is, that I can workaround the issue in EPP by commit JTA transaction and start the new transaction after creating (or deleting) page, so the list of pages in PageManagementPortlet, which is obtained via JCR query, will contain newest results. But I am waiting on opinion from JCR team first.

Comment 2 mposolda 2012-06-29 09:31:24 UTC
I have a fix and sent pull request to GateIn https://github.com/gatein/gatein-portal/pull/60 . I have a fix for EPP as well, but not 100% sure if we can apply it in minor release 5.2.2.