I agree, provided that the abstraction isn't too limiting.
That said, there seem to be a couple of standards heading in that direction already e.g.: wfxml: http://www.wfmc.org/index.html jsr 207: http://www.jcp.org/en/jsr/detail?id=207 cheers, j. On 4/28/06, Jeffrey Puro <[EMAIL PROTECTED]> wrote:
This isn't particularly ServiceMix specific, but eventually I would like to integrate this within the ESB. It appears that with the many BPM engines out there, there is no standard API for accessing each of these. I've heard that there has been talk of creating some kind of project like this, but not sure if anything has been started yet. The project should have the following basic goals: 1. Develop a generic API for accessing any type of BPM engine. The core functions shared across BPM engines should be supported. This will include process creation, signaling, resuming, etc... We can use some sort of Factory pattern to develop this in an extensible fashion. 2. Develop a standard declarative configuration model for starting up BPM engines and interacting with each. One possibility would be to use Spring as the IoC container for wiring the different container specific beans and configurations together. 3. Basic configurations should be as decoupled from the actual BPM engine as possible. This means that the base configuration is always used, like some kind of default while any extra configurations can be added on to get specific BPM features working. The purpose of this is to allow for minimum configuration for getting things started. 4. There should be integrations with the various ESB's out on the market. The benefits of having a BPM and ESB integrate seamlessly are enormous. These two technologies will probably be a core of companies' software stacks, so I see this as being extremely important. Some initial supported ESB's may be things like apache ServiceMix and Mule (yes I said it, our competitor :-) ). As I'm sure there is a lot of talk on this topic already, I'd like to hear people's feedback on this. Regards, Jeff Puro Senior Developer Sterling Testing Systems, Inc. This email (and any attachments) is intended only for the use of the individual or entity named above and may contain information that is privileged and confidential. If you are not the intended recipient, or have unauthorized access, you are hereby notified that copying, disseminating, distributing or taking any action in reliance on this email is strictly prohibited. Opinions, conclusions and other information in this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it.
