Hi guys,
Good points. I'm not sure if I agree with Sebastian when he mention the the
API separation. Right now if we think into an integrated
environment/platform (I'm not saying heavy-weight) the APIs and the
semantics used need to be chosen carefully.
But the main ideas remains the same :
- embeddable
- small footprint
- BPMN2
- pluggeable modules with default implementations
About Maciej thoughts, I notice that you pointed out Sebastian's words and I
notice that both knows Drools only as a Business Rule engine (just Drools
Expert), would be nice to discuss the main points of the other modules of
Drools as well, just to not miss something important.
Greetings.
On Sat, Apr 17, 2010 at 1:11 PM, Maciej Swiderski <
swiderski.maciej(a)gmail.com> wrote:
Hi guys,
I agree with you if we are talking about jBPM as a framework as it is
currently. But in my opinion presented concept is more like complete
platform and not only framework. That's why I suggested that authorization
should be included there as well.
Obviously it should be plug-able but I think this will be done like that by
default.
BTW, it was described already in the article, I just simple missed it.
In addition, it should be clearly shown what is the purpose of jBPM and
Drools. At this point they overlap each other in some areas which makes it a
bit confusing. As Sebastian pointed out, Drools is a good rules engine and
jBPM is a good workflow engine so focus should be on integrating them in a
easy way, that would bring a lot to both.
Regards
Maciej
2010/4/17 Sebastian Schneider <schneider(a)dvz.fh-aachen.de>
Hello Mauricio,
>
> Am 17.04.2010 18:20, schrieb Mauricio Salatino:
> > Hi Sebastian,
> > Not sure about PVM, I think there are some differences with jBPM that
> > need to be addressed.
> > In drools flow there is already an advanced support for BPMN2, so it
> > think we need to dig a little bit to find out big differences and
> > missing points.
>
> Does Drools Flow use a version of the PVM? Anyway, I never understood
> completely what was the point of Drools Flow since in the first place
> Drools is a business rules engine for me - and a good one - but not a
> solution for the execution of complete processes.
>
> I know that there are cases where a busines rule represents a kind of
> flow and this is where Drools Flow fits in for me but I would never
> consider task management part of it for example.
>
> Just my 2 cents
> Sebastian
>
> --
> Sebastian Schneider
> e-mail: Sebastian.Schneider(a)alumni.fh-aachen.de
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
--
-
http://salaboy.wordpress.com
-
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -