<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="x-western">
Drools Flow - 2 nice blogs<br>
<br>
<a class="moz-txt-link-freetext"
href="http://blog.athico.com/2009/01/drools-5-holistic-approach-to-problem.html">http://blog.athico.com/2009/01/drools-5-holistic-approach-to-problem.html</a><br>
<i>"the problem for business people to understand the differences
between business processes and rules, because from the point-of-view of
business use-cases they are integrated. why are there two tools /
frameworks to manage the same thing?<br>
....<br>
Now I read the documentation of Drools 5 and noticed that all is
availabe in ONE product: Drools 5. Thats really great news - I hope I
understood all well and I'll give it a try to do it with Drools only.
This gives me a better feeling than my previous decision. "</i><br>
<br>
<a class="moz-txt-link-freetext"
href="http://blog.athico.com/2009/01/drools-flow-and-osworkflow-migration.html">http://blog.athico.com/2009/01/drools-flow-and-osworkflow-migration.html</a><br>
<i>"We work together on projects for Argentina's biggest healthcare
provider, who are big OSWorkflow users. However with Drools offering a
much more powerful and complete framework, that integrates rules,
processes and event processing there is now a desire to move to this as
the standard. As part of this effort we need a migration path for al
the legacy OSWorkflow applications."</i><br>
<br>
</div>
</body>
</html>