[
http://jira.jboss.com/jira/browse/JBPM-831?page=all ]
Tom Baeyens closed JBPM-831.
----------------------------
Resolution: Rejected
feel free to update the hibernate mappings with explicit id generation strategy when you
use it.
but in the jbpm out-of-the-box downloads, we want it to be as portable as possible. that
is why we opt for the native id generation strategy.
avoid using default id generator
--------------------------------
Key: JBPM-831
URL:
http://jira.jboss.com/jira/browse/JBPM-831
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.1.2
Environment: The problem is common to all platform.
Issue is identifed on Oracle 9.1 specifically.
Reporter: Wenbo Zhu
Assigned To: Tom Baeyens
The Id generator should be named explicitly, which is currently not.
<id name="id" column="ID_"><generator
class="native" /></id>
This will introdcue issue when jbpm schema has to be updated (dropped, e.g.) as the db
may be shared with other apps that uses default hibernate id generator too .. in case of
Oracle, it's "hibernate_sequence".
- Wenbo
--
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