I'd like to point out the generic context implementation already exists in the TemplateService in Fulcrum, and is used in Turbine 3 (and thus in Scarab). I urge you not to give specifics of a generic context path even a moment's consideration, as doing so adds needless complexity and offers very little in return.
Any movement towards a generic context interface should use an opaque type, like Object or an empty marker interface (from what I saw of the recent TorqueComponent impl., Avalon uses these to good effect). Content rendering engines are inherently different, and pretending that they are does not make them so (read: don't fool yourself). Each individual rendering system will do the appropriate thing with its contextual argument. -- Daniel Rall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
