[
http://jira.jboss.com/jira/browse/JBPM-653?page=comments#action_12353769 ]
Tom Baeyens commented on JBPM-653:
----------------------------------
Matej,
i think that if we put classloader or class caching in jbpm, we should have an eviction
policy in place. it would even be better if we could configure the cache size. that
should be possible because we could check the size of the class byte arrays.
without these features, jbpm becomes less scalable. (even though now it is less performant
then with the modifications you give)
but overall that effort becomes a bit big to implement shortly. your point is taken. if
we can find some form of caching that makes sense and which we can implement in a short
period, we'll do it.
regards, tom.
make the process parent classloader configurable
------------------------------------------------
Key: JBPM-653
URL:
http://jira.jboss.com/jira/browse/JBPM-653
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
now, always the jBPM classloader is taken as a parent for the process classloaders. this
should be made configurable. at least one other possibility should be to configure the
context classloader.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira