Or perhaps just the old "Can't Parse Template" error with the line
reported.
On Jul 22, 2005, at 1:58 PM, Henri Dupre wrote:
It would be quite nice if tapestry could at least issue a warning or
even throw an error.
Henri.
On 7/22/05, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote:
I don't see how this is a bug. The "value" attribute is called twice,
so the second one wins. Tapestry isn't responsible for coder errors!
Jamie
On Jul 22, 2005, at 1:01 PM, Geoff Longman wrote:
Posting to the right list..
Geoff Longman wrote:
Is this a bug? Or, more importantly, has this already been
addressed in T4?
<input jwcid="@TextField" value="ognl:emailAddress" .........
value=""/>
Tapestry ignores the first takes the second 'value' attribute
and
creates a static binding. Of course, when the form submits,
there is a
binding exception 'cuz you can't set a value on a static binding.
Geoff
---------------------------------------------------------------------
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]
