Aleksander,
jBPM itself always relies on the DB for concurrency and transaction handling.
If jBPM caches something, it means that information is considered static. Process definitions are static.
When a new version of a process definition is deployed, it is stored NEXT to the old version. Both are kept in the DB. so the old version doesn't change.
That is why jBPM can cache process definitions in memory.
Whenever a process definition is being used, it is verified that it still exists in the DB. If not, it is removed from the cache.
hth
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255455#4255455
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255455
Hi All,
I tested the jbosscache-pojo-3.0.0.GA and jbosscache-core-3.2.0.GA successfully through ANT script.But I want to use this feature in my new j2ee application ( JSF,EJB,ICEACES,Hibernate ,EJBCA and Spring application).Can any body from this community can give me any idea how can I able to integrate both.One more question ,Which is better app server among Jboss application server and Glashfish for Jboss Cache.Please give me your valuable suggestion so that I can do further developement using Jboss Cache with one of the app server.
Thanks in advance
Sandy
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255441#4255441
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255441