On that note,
Is there documentation or example somewhere on how to persist long-
running workflow tasks? I've been reading about the ruleflow and it
seems to be great that workflow and rules can be integrated into one.
To me, this means one less application/server to worry about and one
less API system to learn.
However, based on what I've been seeing so far, ruleflow is a purely
in-memory deal. I have read some discussions that it's possible to
persist the workflow for long-running tasks (ie. days). How would I
go about doing this or learning about this?
Thanks.
-ck
On Dec 22, 2008, at 5:11 AM, Mark Proctor wrote:
Mark Proctor wrote:
> We published a combined M3/M4 release notes summary, sorry in the
> late delay.
>
http://blog.athico.com/2008/12/drools5-m3-release-notes.html
Just as a state of play. I plan to do one more M5, hopefully
tomorrow, which will contain changes for the Pipeline and DataLoader
api. Which will facilite loading data from non pojo sources as well
as hooking up to things like JMS, which is especially important for
Fusion. Then I'm aiming for a CR1 for Dec31st, fingers crossed :)
Mark
>
> Mark
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users