[esb-issues] [JBoss JIRA] Commented: (JBESB-1435) Message longer than 255 chrs cannot be passed to jBPM
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Thu Jan 10 12:38:43 EST 2008
[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394607 ]
Kevin Conner commented on JBESB-1435:
-------------------------------------
The reason for the discrepancy is a conflict between the hibernate definitions for HibernateStringInstance.hbm.xml, StringInstance.hbm.xml and (potentially) JcrNodeInstance.hbm.xml.
Each of these VariableInstance subclasses map entries onto the JBPM_VARIABLEINSTANCE using the same field, STRINGVALUE_, but only StringInstance.hbm.xml specifies the length. The length is obviously being ignored when the DDL files are created as the HIbernateStringInstance.hbm.xml is being loaded first.
> Message longer than 255 chrs cannot be passed to jBPM
> -----------------------------------------------------
>
> Key: JBESB-1435
> URL: http://jira.jboss.com/jira/browse/JBESB-1435
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Process flow, Rosetta
> Affects Versions: 4.2.1 CP1
> Reporter: Jiri Pechanec
> Assigned To: Kurt Stam
> Priority: Blocker
> Fix For: 4.2.1 CP1
>
> Attachments: server.mysql.log.gz, server.oracle10g.log.gz
>
>
> If message is String it and passed to jBPM then it is stored in variable instance that is limited by 255 chars length.
> This should either be fixed or clearly stated in the dosumentation and removed from quickstarts not to support antippaterns.
--
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
More information about the esb-issues
mailing list