[rules-users] Drools Flow: Validation Chain Approach

[David Sinclair]

Hi Anatoly,

Just saw your original post.

"
    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":

               Validation One Node
                            ||
                            \/
                       SPLITTER => Finalize => End ( or Fault node, which is
as dirty )
                            ||
                            \/
               Validation Two Node
                            ||
                            \/
                       SPLITTER => Finalize => End
                            ||
                            \/
               Validation Three Node
                            ||
                            \/
                       SPLITTER => Finalize => End
                            ||
                            \/
               Validation Four Node
                            ...
                            ...

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?

dave


On Wed, Jun 2, 2010 at 2:29 PM, tolitius <webakaunt at gmail.com> wrote:

>
> well, I guess that depends on a use case.
>
> What if you want to have some skip / retry policy in place?
>
> Also a workflow client ( that called this process ) now need to be aware
> that somewhere inside this process ( subflow of a subflow of a subflow... )
> there is a ValidationException that will be thrown: not a nice way to have
> your workflow APIs built.
>
> But if it works for you, it is fine. I just find it really strange that
> Drools Flow fails to see the importance of Java exceptions, e.g. there is
> no
> way to register a real [ Java ] exception handler to the process.
>
> The only two non-existing at this moment solutions for the flow above would
> be:
>
> 1. Use a process ( / subprocess ) wide Java exception handler, that you can
> register ( e.g. ValidationExceptionHandler ), that would know exactly what
> to do in case an exception occurs.
>
> 2. Use Activities ( e.g. work items ) that are capable of more than one
> transition coming out of them, and use the second transition to point to
> the
> Validation Error
>
> I still need to set some time aside to think of some other solutions, but I
> would appreciate some external thoughts as well.
>
> Thank you,
> /Anatoly
> --
> View this message in context:
> http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Validation-Chain-Approach-tp861911p865551.html
> Sent from the Drools - User mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20100602/f90a847e/attachment.html