[
http://jira.jboss.com/jira/browse/JBPM-831?page=comments#action_12356078 ]
Wenbo Zhu commented on JBPM-831:
--------------------------------
It's fine to rely on the native id generation . .but the generator needs be named
explicitly (ideally), to something like <generator class="native"
name="jbpm_id_generator">. Otherwise, in a production system, a jBPM schema
upgrade will wipe out the existing id-generator (such as Oracle hibernate_sequence) that
may be used by other systems.
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