I'm looking for a way to tune the second level cache of jBPM (3.2.2) according
to my needs.
jBPM internally configures the cache concurrency strategy for several
collections as "nonstrict read-write", while I need them "read-only" (to avoid
prohibitive synchronization cost and eventual errors
Indeed I mean replacing :
list name="exceptionHandlers" cascade="all"
by :
list name="exceptionHandlers" cascade="all" lazy="false"
(html problem)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068828#4068828
Reply to the post :
http://www.jboss.com/
Same problem with jBPM 3.1.4.
Simply replacing :
with :
in all hibernate mapping files (*.hbm.xml) seem to have solved the problem for
me.
I can't figure out why an exception handler should be lazy-loaded anyway. It
seems so unsafe...
Hope this helps.
View the original post :
http
