Hey Folks.
I know that this has been brought up a few times, and I have poked
through the Wiki and this group and can not find an answer. Can you
confirm that something like this is not currently supported in 1.6,
but is coming in 1.8?
<event-handler event="...." >
<event-mapping event="denied" mapping="Site.ViewDenied"
redirect="true" />
<event-mapping event="accepted"
mapping="Site.ViewAccepted"
redirect="true" />
<notify listener="ContactsListener" method="........"/>
</event-handler>
That is, the event-mapping tag will support an attribute "redirect",
and maybe even "redirectArgs" and will turn any event announced in the
listener that matches the "event" attribute into a redirect event.
This is instead of doing:
<event-handler event="...." >
<event-mapping event="denied"
mapping="redirect_to__Site.ViewDenied"/>
<event-mapping event="accepted"
mapping="redirect_to__Site.ViewAccepted" />
<notify listener="ContactsListener" method="........"/>
</event-handler>
... And having two separate handlers "redirect_to__..." simply used to
handle the redirect.
Last I've hard, there is only support for a new (in 1.8) "redirectEvent
()" method at the listener level. This is an improvement, but I think
that defining that kind of flow is best expressed at the config level
through the event-mapping tag. Anyone else agree? This way the
listeners can simply go on with "announceEvent("accepted")" all the
while oblivious to the fact that we are actually issuing a redirect
instead of pushing that flow logic down into the listener layer.
Just my $0.02.
-Brian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
-~----------~----~----~----~------~----~------~--~---
