[jboss-jira] [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility

[Alejandro Guizar (JIRA)]

     [ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]

Alejandro Guizar updated BPEL-230:
----------------------------------

    Workaround Description: Replace jbpm-bpel.jar in the base directory of the distribution with the attached file. Rebuild the service archive as described in the documentation.
               Description: Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.   (was: Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the JDBC type LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently. )
                Workaround: [Workaround Exists]

Changing the column type in org.jbpm.bpel.db.type.ElementType from LONGVARCHAR to VARCHAR causes Hibernate to generate a column of length 255. Such a short length is likely to be insufficient for most applications. For this reason, all ElementType occurrences were given an explicit length of 4000. This figure is consistent with jBPM's "long" text columns. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmDbCompatibility.

The attached jar has the above changes applied.

> store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
> --------------------------------------------------------------------------------------------
>
>                 Key: BPEL-230
>                 URL: http://jira.jboss.com/jira/browse/BPEL-230
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1.GA
>
>
> Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently. 

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