You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Geoff Longman <gl...@gmail.com> on 2005/07/22 17:53:14 UTC
Possible Bug?
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
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Geoff Longman <gl...@gmail.com>.
It should be handled in the TemlateParser with the standard exception
Geoff
On 7/22/05, Henri Dupre <he...@gmail.com> wrote:
> On 7/22/05, Jamie Orchard-Hays <ja...@dang.com> wrote:
> > Or perhaps just the old "Can't Parse Template" error with the line
> > reported.
>
> That would be good enough! The AttribuedDeclaredTwice would be even
> nicer but either one would help alot.
>
> Henri.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Henri Dupre <he...@gmail.com>.
On 7/22/05, Jamie Orchard-Hays <ja...@dang.com> wrote:
> Or perhaps just the old "Can't Parse Template" error with the line
> reported.
That would be good enough! The AttribuedDeclaredTwice would be even
nicer but either one would help alot.
Henri.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
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 <ja...@dang.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
You mean like, "AttributeDeclaredTwiceException" or something like that?
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 <ja...@dang.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Henri Dupre <he...@gmail.com>.
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 <ja...@dang.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Kevin Menard <km...@servprise.com>.
On Jul 22, 2005, at 1:39 PM, Jamie Orchard-Hays 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!
I'll agree to a certain extent. Clearly though, the programmer
shouldn't use the same attribute twice, so providing a useful error
message is key. Assuming the user somehow decided he didn't actually
want the first attribute value is odd behavior.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Template Parser Bug?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
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: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tapestry-user-
>>> help@jakarta.apache.org
>>>
>>>
>>>
>>
>>
>> --
>> The Spindle guy. http://spindle.sf.net
>> Get help with Spindle:
>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
>> Announcement Feed:
>> http://www.jroller.com/rss/glongman?catname=/Announcements
>> Feature Updates: http://spindle.sf.net/updates
>>
>>
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Announcement Feed:
> http://www.jroller.com/rss/glongman?catname=/Announcements
> Feature Updates: http://spindle.sf.net/updates
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Possible Template Parser Bug?
Posted by Geoff Longman <gl...@gmail.com>.
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: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Announcement Feed:
> http://www.jroller.com/rss/glongman?catname=/Announcements
> Feature Updates: http://spindle.sf.net/updates
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Possible Bug?
Posted by Geoff Longman <gl...@gmail.com>.
Actually, since Spindle uses the TemplateParser as is, there's not
really anything I can do about this issue in Spindle.
Geoff
On 7/22/05, Geoff Longman <gl...@gmail.com> wrote:
> Yes of course it is a TODO for Spindle.
>
> I meant to post this to the dev list. Sorry for the noise.
>
> Geoff
>
> On 7/22/05, Paul Ferraro <pa...@gmail.com> wrote:
> > I would expect the template parser to throw an exception in this case.
> > A tag should not be allowed to specify the same attribute twice.
> > As far as I know, this has not yet been addressed in 4.0. I would go
> > ahead and create a jira entry.
> >
> > In the meantime, it would be great if Spindle could flag this as a
> > "warning".
> >
> > Paul
> >
> > 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: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Announcement Feed:
> http://www.jroller.com/rss/glongman?catname=/Announcements
> Feature Updates: http://spindle.sf.net/updates
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Possible Bug?
Posted by Geoff Longman <gl...@gmail.com>.
Yes of course it is a TODO for Spindle.
I meant to post this to the dev list. Sorry for the noise.
Geoff
On 7/22/05, Paul Ferraro <pa...@gmail.com> wrote:
> I would expect the template parser to throw an exception in this case.
> A tag should not be allowed to specify the same attribute twice.
> As far as I know, this has not yet been addressed in 4.0. I would go
> ahead and create a jira entry.
>
> In the meantime, it would be great if Spindle could flag this as a
> "warning".
>
> Paul
>
> 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: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Possible Bug?
Posted by Paul Ferraro <pa...@gmail.com>.
I would expect the template parser to throw an exception in this case.
A tag should not be allowed to specify the same attribute twice.
As far as I know, this has not yet been addressed in 4.0. I would go
ahead and create a jira entry.
In the meantime, it would be great if Spindle could flag this as a
"warning".
Paul
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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org