Redirect command should support ${} syntax for args and persistArgs attributes

[peterfarrell]

Redirect command should support ${} syntax with support for defaults for args, event, module, args and persistArgs attributes. This would be inline with how the new call-method command works.

Let's pretend there is an assessmentBattery CFC in an event arg named assessmentBattery and I need to the jobProfileId from that CFC on an redirect. This is not currently possible, but would be very helpful:

<redirect event="webAssess.jobProfiles.displayProfile" args="jobProfileId=${event.assessmentBattery.jobProfileId}:0" />

[kurtwiersma]

Yes I think this is a great idea of another place to leverage the expression syntax. I would just have your example use ${event.assementBattery.jobProfileID:0} since I think we usually use the colon inside the {} to indicate defaults.

[kurtwiersma]

Closed as part of changeset 1341.

[kurtwiersma]

Now that I have completed this I am wondering if we should support expression syntax in the event attribute as well. That way you could have a listener fill in an event arg which could be the event name to redirect to. I realize that ticket #30 allows you do it programatically inside a listener (which is very nice) but I am always looking for ways to do less inside the listeners so I can see the whole flow of my app by looking at the xml file. Do guys have any other thoughts?

[peterfarrell]

I agree that event (actually, module and persistArgsIngore) should allow for the EL syntax.

Kurt, does this work as well?:

<redirect event="displayProfile" args="${event.assessmentBattery.id:0}" />

That the arg in the url would be id without explicitly defining the key for the value?

Also, I think we will need to expand <redirect> to work with routes now as well.

[peterfarrell]

Kurt, see comment:7:ticket:30 for information on adding redirectRoute() method to the EventContext with a helper method redirectRoute() in the BaseComponent that calls the method in the EventContext.

[peterfarrell]

As discussed via IM, we should support nested args and persist-arg for redirect just like we do for call-method. Something like:

<redirect event="doSomething" persist="true">
  <arg name="id" value="${event.assessment.assessmentId}"/>
  <persist-arg name="someBean" value="${event.assessmentBean}"/>
</redirect>

[kurtwiersma]

[None] - Added support for expressions in the module, event, and url attributes of the RedirectCommand?. refs #203

[kurtwiersma]

[None] - Support for nested arg and persist-arg tags inside redirect. closes #203

[kurtwiersma]

[None] - Updated to include the new arg and persistArg tags in the config xml refs #203