I think that's a dangerous ambiguity. The difference between prop: and
literal: here could easily bite you (especially in your example, since we're
talking about server-side generated names of client-side functions).
On 5/6/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
Wouldn't be useful to have the informal parameter of components looked
up as the were parameter?
I mean i could have a
<t:any element="span" onclick="onClickFromUser">${user.id}</t:any>
and on the corrisponding java class page something like:
public String getOnClickFromUser()
{
return "myFunctionName(" + user.getId() + ");";
}
If the class hasn't a corresponding method the parser will print the
string as is, as it does now.
Is this worth a jira issue?
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
