[esb-issues] [JBoss JIRA] Commented: (JBESB-1435) Message longer than 255 chrs cannot be passed to jBPM

[Jiri Pechanec (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394486 ] 
            
Jiri Pechanec commented on JBESB-1435:
--------------------------------------

1) The problem is that 255 chars length is set on ESB sql create scripts
2) The second problem is that for us/customer it means that we cannot pass message with arbitary length to jBPM

So as I see it we should
1) Modify the SQL scripts so it will allow maximum string length for each database
2) Document the limitation about message length
3) Educate customer that if he requires to process long messages then he should
      - either use message store and pass only UUID to it between services
      - use ByteArray approach and pass message as byte array

      

> 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