And putting everything in the REQUEST scope is not really the "object oriented" way of doing things.
It doesn't really de-couple things very well.
What advantage does this type of "decoupling" offer?
The execution method of the rule will always be executed in the presentation layer in the context of the container. It will always have access to the REQUEST scope. As long as parameters are optionally present in the REQUEST scope there isn't even any chance of breaking its normal mode of operation.
To me, compelling the container tag, container object and rule object to understand the concept of a passthrough set of parameters seems to be a bit obtuse.
But heh, I'm ready to be convinced otherwise ;)
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
