[
https://jira.jboss.org/jira/browse/JBPORTAL-2215?page=com.atlassian.jira....
]
Thomas Heute commented on JBPORTAL-2215:
----------------------------------------
The underlying issue is that jBPM doesn't let you use a HibernateSessionFactory and
will start its own based on hibernate.cfg.xml.
It's then difficulty to build programatically the HibernateSessionFactory and pass it
to jBPM as we do for other services.
For the moment, we will only start the workflow tests with hsqldb.
CMS Module TestSuite JBoss Unit Environment not setup properly for
Workflow multi-db tests
------------------------------------------------------------------------------------------
Key: JBPORTAL-2215
URL:
https://jira.jboss.org/jira/browse/JBPORTAL-2215
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS, Portal QA
Affects Versions: 2.7.0 CR1
Reporter: Sohil Shah
Assignee: Prabhat Jha
Fix For: 2.7.0 Final
This is a Test Suite environment setup issue. For the workflow tests, the JBPM Hibernate
environment is setup outside the hibernates.xml/datasources.xml combination used by
jboss-unit to run the tests in multi-db mode.
There are a couple of issue that are caused by this out-of-sync JBPM Hibernate
environment setup
1/ The proper Hibernate dialect is not selected in a parameterized manner used by the
JBoss Unit environment
2/ There are locking issues during test setUp and tearDown requiring commenting out the
"session.flush" calls inside
"org.jboss.portal.cms.hibernate.HibernateStore". But this is a test environment
cleanup issue, and the actual code that is shipped requires the manual flushing due to
Blob issues with Oracle and Postgresql drivers (see here for details:
https://jira.jboss.org/jira/browse/JBPORTAL-983)
For now, the CMS Module testsuite should run all tests in multi-db mode, and the workflow
tests in hsqldb only
Note: The same module when run in a non-jboss-unit test environment under 2.6 runs
successfully with all supported databases
--
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