Tom and I have spent today talking about integration of various
projects, ours included. I think there is a lot we can do with
integration now without waiting for the next release of jBPM.
Mark.
On 26 Mar 2007, at 13:25, Burr Sutter wrote:
My point is we have plenty of time to worry about this issue
considering the jBPM team has a really long term set plan (a
rewrite to be multi-process language focused) plus the fact that it
has a human-centric workflow concern that is less directly related
to the needs of the ESB.
Now, we can certainly discuss how much more important are the needs
of the ESB vs things like multi-language and human task management.
Please sell me on the idea of lifecycle as it relates to jBPM. The
instantiation and manipulation of a jBPM process is primarily a
series of database transactions.
Bill Burke wrote:
>
>
> Burr Sutter wrote:
>> jBPM 4.0 isn't due until late Q1/early Q2 2008. If we had
>> specific requirements we might be able to get the jBPM team
>> focused on a deliverable between now and and then but the
>> challenge for jBPM is focus: human-centric BPM/workflow or
>> service-centric orchestration.
>
> Again, i think the changes to jBPM that ESB needs are a
> fundamental thing that the jBPM team needs anyways. Like lifecycle.
>
> Man, you're full of excuses.
>
> Bill
_______________________________________________
esb-dev mailing list
esb-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/esb-dev