[Design of JBoss ESB] - Re: Fixing classloading issues in jBPM with CL-Registry?
by Kevin.Conner@jboss.com
The current jBPM issues are related but it is just part of a bigger issue with jBPM.
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.
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 these issues.
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 undeployed/redeployed. This will necessitate proper support for classloader hierarchies, scoped deployments etc.
I should also add that I do not think that ESB is the correct location for this work, although we would have to modify some code to fit in with whatever is decided.
Kev
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179330#4179330
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179330
16 years, 2 months
[Design of JBoss jBPM] - Re: community branch
by tom.baeyens@jboss.com
"kukeltje" wrote : sure, but who is going to monitor that? Merge it? Even after 4.0. People can add functionality without adding testcases, docs or whatever, like Tom mentiones. Is e.g. test coverage going to be part of releases as well. Do these people also need to sign the contributor assignment ? If not, JBoss might get in trouble with copyright infringements.
all the requirements will be just as they are now. in fact, we'll make the requirements much more clear to contributors.
we should document clearly what we expect :
* link to jira issue
* code updates
* test coverage
* docs updates
* xsd schema updates
* and so on
the more complete work a contributor delivers, the easier it is for us to merge the change into the project trunk branch.
if people do not submit complete work (which they can) then it depends on whether someone else takes their work and finishes it. that could be other people from the community or people from the jbpm team itself.
this would allow us to give svn access very easily so that people can just give it a go. and on the other hand, it allows us to adopt only the contributions which we think are mature enough to enter the project/product.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179292#4179292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179292
16 years, 2 months