anonymous wrote : Have you looked at the classloader issue(s) in ESB/SOA-P that relate to
I am not sure if I found all of them, do you have concrete issues in mind? Can you maybe
post the links which I shouldn't miss?
anonymous wrote : The current codebase appears to be based on the premise that each jBPM
instance is standalone and co-located with the code running within the system but this is
not valid in an environment like the AS which can rely on a shared codebase.
Exactly! This is what I want to address with this...
anonymous wrote : The notion of a jBPM deployer is an interesting one and is something
that I have mentioned in the past. It is likely to be the keystone in any real solution to
Glad to hear that :-) Some evidence that we both are on the right track....
anonymous wrote : What is really missing is for jBPM to define a proper lifecycle for the
processes in a shared environment, including support for artifacts which can be
Sorry, I didn't get that completly. You mean for the processdefinition-XML's? Or
what to include in what lifecycle (classes in EAR, processdefinition.xml in DB, ...)?
anonymous wrote : I should also add that I do not think that ESB is the correct location
for this work
Yeah, I think it fits better in the jBPM corner, same logic fits in a pure AppServer
environment and maybe even the OSGI world or something else... So it is not tied to the
I'm going to have a telco with Tom on this issue on friday, I think he has an oppinion
to that too....
Regards from Berlin
View the original post :
Reply to the post :