[jbpm-dev] Nodes and Process instance are not mapping after persistence

Mauricio Salatino salaboy at gmail.com
Sat Jan 7 12:00:20 EST 2012


Hi Leo.Li,
You should write these questions into the forums not to the dev list.
I will need to read that thread carefully, because ksession as a
singleton doesn't sound good at all
about your questions
2 and 3. the binary data stored is for internal usage, you should
externalize the data that you want about the process execution using
the history logs.
4. not sure what you mean with that.. can you elaborate?

Cheers

On Fri, Jan 6, 2012 at 11:50 PM, Leo.Li <leo87601 at gmail.com> wrote:
> Hello All,
>
> As we investigate and PoC in last two months, we found some unstable problem
> in this platform. (http://community.jboss.org/thread/175443)
>
> We had a template solution to fix this problem, made the Ksession
> as singleton object. But we cannot load the snapshot or new assets easily.
>
> We have following questions:
>
> 1. how to fix this kind of old data?
> 2. Can the JBPM5 store the data as the JBPM4 (RDBMS)?
> 3. Can we have some way to watch the data in PROCESSINSTANCEBYTEARRAY ?
> 4. If we have more than one history snapshot in the same processid(like
> "leadprocess"), can the JBPM5 load the correct history version for my
> instance?
> In other word, we had created the instance1 on snapshot1, instance2 on
> snapsot2. After the third version as the latest package. And than when I'm
> handling the instance1, will they still using the snapshot1 workflow? Or we
> need to coding in our side to achieve this?
>
> It would be nice if you could provide a bit more information on the these
> problem.
>
> Thanks a lots
> Leo
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev
>



-- 
 - CTO @ http://www.plugtree.com
 - MyJourney @ http://salaboy.wordpress.com
 - Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar

 - Salatino "Salaboy" Mauricio -



More information about the jbpm-dev mailing list