Hi George. If I understand what you're trying to do correctly, it's not going to work and you'll need a new approach.
You've stated that you're trying to use <t:outputraw/> but you haven't included the element in your examples. I'm going to have to guess that you've put your component html into a string and are trying to get it into the page. Tapestry processes and compiles your templates when they are first accessed. It's not possible to dynamically change your template by adding a new component. In this case it appears that you're trying to add an eventLink. It looks like what you are doing is disabling the link after the user has clicked it, and probably toggling them when the user clicks the other link (clicking yes disables yes and enables no) You could use the "disabled" attribute of the event link and get a similar effect. Josh On Tue, Jul 31, 2012 at 5:43 PM, George Ludwig <georgelud...@gmail.com>wrote: > I'm trying to use outputraw to render eventlinks, however when I do this > tapestry does not appear to bind the event on the client to the event on > the server. Is there a way to make this work? > > I use outputraw because it would be unwieldy to use Tapestry's <t:if> > construct to control the rendering. Here's a simplified example with a > single row: > > <table> > <tr><td>#business</td><td><a t:type="eventlink" t:event="addYesTerm" > t:context="literal:#business" href="#">yes</a></td><td><a > t:type="eventlink" t:event="addNoTerm" t:context="literal:#business" > href="#">no</a></td></tr> > </table> > > If I click on the "yes" eventlink, the table should re-render like this: > > <table> > <tr><td>#business</td><td>yes!</td><td><a t:type="eventlink" > t:event="addNoTerm" t:context="literal:#business" href="#">no</a></td></tr> > </table> > > If I then clicked on the "no" eventlink, the table should re-render like > this: > > <table> > <tr><td>#business</td><td><a t:type="eventlink" t:event="addYesTerm" > t:context="literal:#business" href="#">yes</a></td><td>no!</td></tr> > </table> > > As I said, I think I can make this work with the <t:if> construct, but it > would take a lot of extra coding! >
