Dictionary Triggers

[Randy]

I was playing around with the trigger code a little for
http://trac.cfeclipse.org/cfeclipse/ticket/424 and has a question with
the triggers. Right now, from the examples of the triggers that I was
looking at, they are made to be based off the value of an attribute.
So if the action on the cffile is append then the output becomes
required.

But it doesn't look like there is anyway to check for *any* value
being provided to activate the trigger. It is all bound to look for a
specific value.

This really comes into play when you have the cases such as the
cfheader tag where it is a statuscode *OR* a name. There isn't a
definitive list of what is valid for the name for the trigger, just a
none-blank value.

So, one change that I was thinking we could make to the dictionary
trigger code is to make the ability to have a wildcard (*)? character
that could be used in triggers to mean that it just has to have any
value for the trigger to activate.

Would that be the best way to handle the cases where the tag has
attributes in an either/or but not triggered by a specific value?

Randy

[denstar]

Sounds like a logical approach, but I'm really curious as to what Mark
and the Railo guys have come up with for the dictionary stuff.

IIRC, they were taking CFE into consideration. Neh, Mark?

Might just be generation of Railo tags from their repo.

--
Two quite opposite qualities equally bias our minds - habits and novelty.
Jean de la Bruyere