I've been thinking about this a bit also. I think the simplest way to move forward would be to add a namespace parm like this
@SupportsInformalParameters(namespace=true) This would cause the marked component/mixin to only claim it's namespaced parameters. The ones without a namespace would work the old way. This would preserve backward compatibility and allow new mixins to specify their behavior. With namespace=true on a component that component would always receive the default namespace informal parameters. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Before-I-file-a-JIRA-against-SupportsInformalParameters-tp5456349p5463225.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
