That's why you make your custom component. Or, in tapestry-4.0, you can do as Howard suggested. It would be all of five minutes work (probably closer to 2 or less, with spindle) to create a component that wraps PageLink and sets the renderer once i that component; you can then use your custom component throughout your app /instead/ of page link. Seems a bit simpler an approach than subclassing to return the appropriate link renderer. But, to each his own. :)
Robert Preston L. Bannister wrote: > Specifying a renderer for each PageLink in the HTML would be tedious, > especially given all the links within this application *must* encode > this additional parameter. > > Perhaps I do not understand your meaning. > > Robert Zeigler wrote: > >> Question: why not just specify your custom renderer to the page link >> component? >> >> <a jwcid="@PageLink" page="somePage" >> renderer="ognl:defaultLinkRenderer">Some Link</a> >> >> You could wrap the page link component in your own custom component, >> specify the renderer in your custom component, and then just you your >> AppPageLink (or whatever you decide to call it) throughout your >> application. :) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
