TrustEngine refactoring

[Cantor, Scott]

On 8/20/14, 9:37 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:

>Is there a way to "extend" the DecodeMessage action from the abstract
>flow, just for the SOAP flows, to effectively append the new action on
>the end of the abstract version?  That's what I wanted to do, seemed
>semantically cleanest, but wasn't sure how.

Yes, it's possible, but we'd have to declare a child action-state for the
non-SOAP profiles because the abstract one includes:

<evaluate expression="'proceed'" />


That would short-circuit the additional evaluate step in a child unless it
were removed from the abstract parent version and moved down into the
child flow(s).

Honestly, it's probably easier to just attach a condition to suppress the
action if we really prefer to declare it in the DecodeMessage state.
Basically add an activationCondition-ref that points to a bean that's a
Boolean, and then that bean name is defined in each of the flows to be
true or false.

I would still like to figure out why it's not working in the other spot
though, it usually means something may be off.

-- Scott