[
http://jira.jboss.com/jira/browse/JBPORTAL-1626?page=comments#action_1237... ]
Sohil Shah commented on JBPORTAL-1626:
--------------------------------------
The workaround is not needed anymore. The JBossCachePersistenceManager is made compatible
with 1.4.1. Everything should work out-of-the-box in JBoss AS 4.2.1
FIrst access to a CMS HTML file through /content/ results in a NPE
------------------------------------------------------------------
Key: JBPORTAL-1626
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1626
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.1 Final
Reporter: Thomas Heute
Assigned To: Sohil Shah
Priority: Critical
Fix For: 2.8 Final, 2.6.2 Final
To reproduce, after startup go to:
http://localhost:8080/portal/content/default/project.html
It will fails to acquire a read lock resulting in a null content.
It fails when trying to do:
VersionHistory vh = contentNode.getVersionHistory();
in ContentGetCommand
On the second rendering it will succeed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira