[
https://jira.jboss.org/jira/browse/JBPM-1925?page=com.atlassian.jira.plug...
]
Thomas Diesler updated JBPM-1925:
---------------------------------
Description: * CLOB/BLOB Process Variables: Customers want the size of a process
variable increased, at least allow for a large one that is lazy loaded with the process
instance. The goal is to shove whole SOAP payloads or business objects (e.g.
PurchaseOrder) in there. I mentioned that this isn't a "best practice" but
their issue is that business data & process data are in 2 different DBs and gaining
access to the business data can some times be tricky. (was: * CLOB/BLOB Process
Variables: Goldman wanted the size of a process variable increased, at least allow for a
large one that is lazy loaded with the process instance. The goal is to shove whole SOAP
payloads or business objects (e.g. PurchaseOrder) in there. I mentioned that this
isn't a "best practice" but their issue is that business data & process
data are in 2 different DBs and gaining access to the business data can some times be
tricky. )
CLOB/BLOB Process Variables
---------------------------
Key: JBPM-1925
URL:
https://jira.jboss.org/jira/browse/JBPM-1925
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
* CLOB/BLOB Process Variables: Customers want the size of a process variable increased,
at least allow for a large one that is lazy loaded with the process instance. The goal is
to shove whole SOAP payloads or business objects (e.g. PurchaseOrder) in there. I
mentioned that this isn't a "best practice" but their issue is that business
data & process data are in 2 different DBs and gaining access to the business data can
some times be tricky.
--
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