Nope, they apply at different times. The p: namespace is used when Tapestry parses the template. Later, when it is loading the page and assembling the components, it can tie a named parameter block in a page (or container) template to a parameter of a component within the template.
Interestingly, it may be a bug that @SupportsInformalParameters is needed when the parameter block is being plugged into a formal parameter (a declared parameter, via @Parameter on a component field). That should only be necessary for components such as BeanEditor/BeanEditForm and Grid, where the parameters that will be passed into the component are figured out dynamically, based on naming conventions (matching properties of a specific object to block parameters). On Wed, Apr 25, 2012 at 3:52 PM, Chris Mylonas <ch...@opencsta.org> wrote: >> Your component needs to have the @SupportsInformalParameters annotation so >> <p:xxx> elements are recognized as block parameters. > > > Just a quickie, > > Is this an alternative method than declaring the "p" at the top of the tml > file - namespace? > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
