Hmm .. for what I remember the variables if are configured to be persisted
using JPA using the Strategies, probably are externalized. Are you sure that
are not being persisted with variable persistence strategy rigth now?
2009/11/18 Vijay K Pandey <VPandey(a)mdes.ms.gov>
If “a” is correct – may be I can customize the “JPAWorkItemManager”
for
my usage? Am I on the right path or I am missing something.
Thanks
Vijay
------------------------------
*From:* rules-users-bounces(a)lists.jboss.org [mailto:
rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Vijay K Pandey
*Sent:* Wednesday, November 18, 2009 4:15 PM
*To:* Rules Users List
*Subject:* [rules-users] Drools Flow 5.1.0.M1 - Persistence - WorkItemInfo
Entity
I have a question related to the (*Drools Flow 5.1.0.M1 - Persistence*) on
the data that gets stored as part of the *
org.drools.persistence.processinstance.WorkItemInfo.*
* *
a) If I am using variable persistence strategy – and I pass a JPA
Entity(stored in its own table) to a *session.startProcess*(“”, map) and
map this entity variable to a parameter in the work item node – then this
entity will get stored in the WorkItemInfo table as a part of the serialized
form in the column (workItemByteArray). So if that is true we have got the
same data stored twice? Is this correct?
b) If “a” is true how can we avoid storing in the WorkItemInfo – is
there somehow we can map the JPA entity to the WorkItemInfo – so that it
doesn’t gets stored twice?
Thanks
Vijay
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
-
http://salaboy.wordpress.com
-
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -