Hi, Nafise --
of course it supprots bpel , and in contrast with pxe
it offers a worklist handler too (it is realy
important for me ),also it merged with agila for
making a better project in bpm area. Agila will have
two major components: Agila BPEL (Twister) and Agila
BPM. The first is the Web Service orchestration
solution based on the WS-BPEL specifications and the
second is an end-user oriented workflow. !
The decision not to include a worklist handler in PXE was a conscious
one with two key motivations:
1) There are plenty of nice (open source and not) workflow systems
out there (like OpenWFE, OSWorkflow, Shark, etc.).
2) There are a lot of features that one could reasonably ask of a
workflow component. For example, integration with an enterprise
directory for escalations, a nice inbox with a calendar to group
entries, etc.
Or, put another way, our goal with PXE was always a *whole* BPEL
engine and no fractions of anything else.
BUT! With JBI, this isn't an issue. The right thing to do w.r.t.
ServiceMix and the difference between BPEL and traditional worklist-
driven user task endpoints is to wrap up your favorite worklist as a
*JBI* endpoint and get it working in ServiceMix. I can't think of
any good reasons that it should be walled-off within the BPEL
component, and I can think of any number of reasons that it shouldn't
be...
My $0.02 on the topic.
-- Paul
