I don't consider it pollution. It seems like meta data to me --- if it really is static data that applies to any potential user.
I've been known to define annotations that are simplified replacements for @Meta, and ComponentClassTransformWorkers that use that meta data to drive some other concern, typically security (which user roles may access such-and-such a page). I've been thinking of adding something similar to see if a component contains a particular event handler for a particular event type (and source component id), which could be used to optimize a lot of server-side processing. On Fri, Jun 20, 2008 at 9:45 AM, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > I'm asking for a hint. > > It's wise or at least not stupid to 'pollute' the page meta-data > (MutableComponentModel model.setMeta) with information about event > handlers method which could be used at runtime to check if a > particular user is able to perform that particular action? > > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
