-
1. Re: The process class loader issue
kukeltje Aug 11, 2006 4:07 AM (in response to yxyang)Yang,
This is such a simple thing to try first, that we would appreciate that very much. If things go not as expected, please report back -
2. Re: The process class loader issue
yxyang Aug 11, 2006 4:38 AM (in response to yxyang)"kukeltje" wrote:
Yang,
This is such a simple thing to try first, that we would appreciate that very much. If things go not as expected, please report back
:-) I found that kukeltje has always blur response:)
i will try of course.
yang -
3. Re: The process class loader issue
kukeltje Aug 11, 2006 10:41 AM (in response to yxyang)Thank you ;-)
-
4. Re: The process class loader issue
yxyang Aug 11, 2006 10:08 PM (in response to yxyang)the question has an answer now:
(1)jbpm.sar classloader is using jbpm.sar classload repository.
(2)So, consider to configure your own project like .ear or .war.... to use the same classload repository. Then ActionHander classes which are deployed as .par file are able to invoke the ejbs deployed seperatly.
yang -
5. Re: The process class loader issue
kukeltje Aug 12, 2006 7:07 AM (in response to yxyang)1) There is a jira issue to make this configurable. So the jBPM classloader uses the context classloader (and I think that should be 'as wel as the processrepository classloader)
2) Would my remark on 1) solve that?
A question from me: Did you achieve what you want or not? -
6. Re: The process class loader issue
yxyang Aug 13, 2006 5:45 AM (in response to yxyang)I already achieve what i want to do.
Actually, there is no problem for the jboss software itself. THe problem is more on the confusion of how to use the jboss components when classloader involves.
TO make the classes in .par file be able to access the class in ejbs, make sure the two parts use the same classloader.
yang -
7. Re: The process class loader issue
kukeltje Aug 13, 2006 7:12 AM (in response to yxyang)would you mind sharing what you did, so others can learn from it?