Hi Robert, Yep, that works too. Easier than hacking tapestry code.
Thanks John -----Original Message----- From: Robert Zeigler [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 2:43 PM To: Tapestry users Subject: Re: XTile Tapestry 4.0 update Ah, y'know, I noticed that with the script component a little while ago (I'm not on the tap dev. team, though. ;) But, here's something else i noticed that I liked even better. :) Instead of passing a map, you can specify the symbols directly as informal attributes of the script component (at least in 3.0.x... I haven't tried this on 4.0). So, doing something like: <script jwcid="@Script" userName="ognl:visit.user.name"/> and then in your script spec: ... alert('user is $userName'); ... actually works, or, does in 3.0. :) HTH. Robert seloha . wrote: > Thanks John, > > The problem I have with the org.apache.tapestry.html.Script patch is > that it makes symbols a required parameter for all Scripts. Is this > correct? > > I made a simple check on the Script component in a page and found that > it definitely is not passing the symbols Map to the script. > > Have you taken this issue further with the Tapestry development team, > since I think they need to know about it? > > Paul > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
