Hi Anatoly,<br><br>Just saw your original post.<br><br>"<span class="ul-threaded" style="margin: 0.5em 0pt 0pt -20px;"><span class="text-cell"><br>
What would be your approach of a clean way to do it in order to avoid
cluttering the process definition with a splitter after individual
"Validation XYZ Node":
<br><br> Validation One Node
<br> ||
<br> \/
<br> SPLITTER => Finalize => End ( or Fault node, which is as dirty )
<br> ||
<br> \/
<br> Validation Two Node
<br> ||
<br> \/
<br> SPLITTER => Finalize => End
<br> ||
<br> \/
<br> Validation Three Node
<br> ||
<br> \/
<br> SPLITTER => Finalize => End
<br> ||
<br> \/
<br> Validation Four Node
<br> ...
<br> ...
<br><br>Could the validations be done in rules as opposed to individual nodes? And then have a single splitter that check the value of some object to determine whether to exit or not?<br><br>dave<br><br></span></span><br>
<div class="gmail_quote">On Wed, Jun 2, 2010 at 2:29 PM, tolitius <span dir="ltr"><<a href="mailto:webakaunt@gmail.com">webakaunt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
well, I guess that depends on a use case.<br>
<br>
What if you want to have some skip / retry policy in place?<br>
<br>
Also a workflow client ( that called this process ) now need to be aware<br>
that somewhere inside this process ( subflow of a subflow of a subflow... )<br>
there is a ValidationException that will be thrown: not a nice way to have<br>
your workflow APIs built.<br>
<br>
But if it works for you, it is fine. I just find it really strange that<br>
Drools Flow fails to see the importance of Java exceptions, e.g. there is no<br>
way to register a real [ Java ] exception handler to the process.<br>
<br>
The only two non-existing at this moment solutions for the flow above would<br>
be:<br>
<br>
1. Use a process ( / subprocess ) wide Java exception handler, that you can<br>
register ( e.g. ValidationExceptionHandler ), that would know exactly what<br>
to do in case an exception occurs.<br>
<br>
2. Use Activities ( e.g. work items ) that are capable of more than one<br>
transition coming out of them, and use the second transition to point to the<br>
Validation Error<br>
<br>
I still need to set some time aside to think of some other solutions, but I<br>
would appreciate some external thoughts as well.<br>
<br>
Thank you,<br>
/Anatoly<br>
<font color="#888888">--<br>
View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Validation-Chain-Approach-tp861911p865551.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Validation-Chain-Approach-tp861911p865551.html</a><br>
Sent from the Drools - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</font></blockquote></div><br>