[jboss-jira] [JBoss JIRA] Updated: (JBPM-1033) string_max parameterization doesn't work

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-1033?page=all ]

Tom Baeyens updated JBPM-1033:
------------------------------

    Fix Version/s: jBPM jPDL 3.2.2

> string_max parameterization doesn't work 
> -----------------------------------------
>
>                 Key: JBPM-1033
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1033
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions:  jBPM jPDL 3.2.1
>         Environment: WIndows XP, Hibernate 3.2.4.sp1, Java 1.4.2
>            Reporter: tmullett
>         Assigned To: Tom Baeyens
>             Fix For: jBPM jPDL 3.2.2
>
>
> Fields in the hibernate mapping files declared as type "string_max" should be truncated to the parameterized length. The mapping files do this parameterization with a "length" attribute on the property element. It looks like this (from ActionLog.hbm.xml):
> <property name="exception"
>               type="string_max"
>               column="EXCEPTION_"
>               length="4000" />
> 4000 also happens to be what StringMax will use if it can't find or parse its parameterization. We needed to shorten some fields to fit jBpm into MS SQL Server. When we shortened the length, we noticed that the parameter was being ignored, causing jdbc to blow chunks.  org.jbpm.db.hibernate.StringMax.setParameterValues() always gets a null passed in for it's parameters with this setup. To get it to work , we changed it to 
>     <property name="exception" column="EXCEPTION_">
> 		<type name="string_max">
> 			<param name="length">1000</param>
> 		</type>
>     </property>

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