[jboss-dev-forums] [Design of JBoss jBPM] - Re: Making the BPM API more generic?

[mark.proctor@jboss.com]

Drools in M3 in about 3 weeks will be orienting away from a rules centric api to a knowledge centric api - i.e. it will not be process centric either, nor will it be tied to Drools. This has been planned for a while:
http://www.mail-archive.com/rules-dev@lists.jboss.org/msg00757.html

This api will be able to wrap, to some degree, other process engine apis. Our PVM will also be capable of executing their models. As proof of concepts krisv has done partial implementations for BPEL, OSWorkfow and jBPM. BPEL runtime is almost complete (Drools is able to execute most examples), although it has not been wired up to WS and still needs work on XML assignment issues. OSWorkflow and jBPM runtime mappings are about 70% complete.

Diego from OSWorkflow is keen on finishing the OSWorkflow adaption. And I'm hoping someone else will take ownership of the BPEL side - we are in talks with large health organisation that is possible going to lend 2 resources for BPEL and WS-Human-Task implementation. We've checkout the Eclipse BPEL tooling and it's now much more improved and almost complete, making BPEL support with tooling now a possibility.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168496#4168496

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168496