It's usual to generate a direct link with a dummy parameter (like "{0}")
at the server and pass that to the javascript that when needed will replace
{0} with the dynamic parameter.For forms, the @Hidden component (check also its encode parameter) is helpful On 6/26/08, Jim <[EMAIL PROTECTED]> wrote: > Hello, > > Is there a clean way to dynamically (on the client-side) generate Tapestry > Direct/Service/Page links? e.g. if you wanted to generate a link to a > Tapestry listener, but you don't know the parameters until after the page is > rendered, such as if you're generating links/behavior to attach to items > that are retrieved via AJAX. > > I could just "View Source", paste the URL, and hack it. Or I could > dynamically update the fields of a hidden @Form. My concern, however, is > that I'd be locking my application into that specific version of Tapestry -- > it would be comparable to basing logic off of a class's toString() > implementation. > > I'm using Tap 4.1.5, though, so perhaps this is a reasonable risk since > upgrading to Tap 5 would require a near-rewrite anyway? > > Thanks, > Jim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
