It was using prefuseaction initially, and it was running the setup code before
every fuseaction (including do-ed ones)
eg:
<prefusaction>
<include template="start"/>
</prefuseaction>
<prefusaction>
<include template="stop"/>
</prefuseaction>
<fuseaction name="A">
<include template="validate"/>
<if condition="Success">
<true>
<do action="B"/>
</true>
<false>
<do action="C"/>
</false>
</if>
</fuseaction>
<fuseaction name="B">
<include template="b"/>
</fuseaction>
<fuseaction name="C">
<include template="c"/>
</fuseaction>
That causes:
start.cfm
validate.cfm
stop.cfm
start.cfm
b|c.cfm
stop.cfm
Whereas I need:
start.cfm
validate.cfm
b|c.cfm
stop.cfm
Thanks,
Peter
>Use 'prefuseaction' like the DTD says, rather than 'preprocess'.
>Preprocess is the name of a globalfuseactions section and a plugin
>point, and should therefore only exist in fusebox.xml.
>
>cheers,
>barneyb
>
>On 10/31/06, Peter Boughton <[EMAIL PROTECTED]> wrote:
>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four
times a year.
http://www.fusionauthority.com/quarterly
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:258578
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
