[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated

[Jan Scherf (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Scherf updated JBPM-2765:
-----------------------------

    Workaround Description: 
Workaround 1:
- Letting hibernate do the creation of database tables.

Workaround 2 (no good idea, because "signalProcessInstance" can't find ProcessInstance by ExecutionId):
- Use integer-values as "key" in you processdefinition.
e.g. use <process description="myDescription" key="123" name="myProcess" version="0" xmlns="http://jbpm.org/4.3/jpdl">
instead of <process description="myDescription" key="anyString" name="myProcess" version="0" xmlns="http://jbpm.org/4.3/jpdl">

  was:
Workaround 1:
- Use integer-values as "key" in you processdefinition.
e.g. use <process description="myDescription" key="123" name="myProcess" version="0" xmlns="http://jbpm.org/4.3/jpdl">
instead of <process description="myDescription" key="anyString" name="myProcess" version="0" xmlns="http://jbpm.org/4.3/jpdl">

Workaround 2:
- Letting hibernate do the 'upgrade' might work.

                  Priority: Minor  (was: Major)


> With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-2765
>                 URL: https://jira.jboss.org/jira/browse/JBPM-2765
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jBPM 4.3
>         Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables where created using the sql-scripts in ${jbpm.home}/install/src/db/create
>            Reporter: Jan Scherf
>            Priority: Minor
>             Fix For: jBPM 4.4
>
>
> org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
> reason: 
> - DatabaseIdComposer.createId(...) produces datatype string
> - but sql-Skripts create dbid-colums whose datatype is integer
> __________________________________________________________________________________________
> See more Details on: http://community.jboss.org/message/521822
> The reason of this problem can be found in org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid. Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml). As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String ...
> It seems that with the introduction of the id generator these scripts were not updated. 

-- 
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