[
https://jira.jboss.org/jira/browse/JBPM-2524?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-2524:
------------------------------------
@Tom: The use case is embeddability. The generated config assumes that there is only the
jBPM hibernate mapping file, when inreality it is often the other way around.
When someone is using Hibernate in its app, and wants it to integrate with jBPM he will
not use the hibernate cfg produced by jbpm, he will use the hibernate cfg that already
exists.
Otoh, injecting the session factory is a better way to achieve this ... so yes, this is a
dev feature and can be postponed.
But also do note it is 'sugar coating': it is already possible today to insert
your own hibernate cfg, altough you still must copy the jbpm.default.cfg.xml completely
...
extract hibernate reference from jbpm.default.cfg.xml
-----------------------------------------------------
Key: JBPM-2524
URL:
https://jira.jboss.org/jira/browse/JBPM-2524
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.2
make it easier to customize the hibernate configuration
--
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