Yes state is there. For your implementation you can create the high
level API that you want, there's no problem with that right?
I see that we discuss about what the framework should do or not based
on different perspectives. We can continue forever if you do not
switch your perspective. The code is there and it allows you to build
applications applying the mechanisms that work better for you. For
what I know there is no plan to create an API like the one you
mention. (honestly I don't think it worth it, from the project
perspective)
Everything else that I can offer are suggestions to do a real
implentation, but that will requiere as I mention before, knowledge
about your particular domain.
- Ing. Mauricio Salatino -
On Apr 2, 2010, at 23:58, tolitius <webakaunt(a)gmail.com> wrote:
my point exactly.
"state" IS there in framework's ProcessInstance AND in framework's
WorkItem,
hence it IS a framework concern [it is a framework DSL]. Therefore
it needs
to be addressed by straightforward clean and simple APIs.
/Anatoly
--
View this message in context:
http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WOR...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users