You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Cosmin Bucur <co...@gmail.com> on 2006/02/08 03:49:13 UTC
Severe Form bug in tapestry 4.0
I have initially reported this to Tacos , since that's what I'm using
, but then it was confirmed that the problem also shows up in Tapestry
without tacos .
Basically if you have a form :
<form jwcid="@Form">
<span jwcid="field1" />
<a jwcid="save">Save</a>
<span jwcid="field2" />
</form>
Only the fields before the save link get submited , the rest are
ignored , and not saved to the data obj .
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Severe Form bug in tapestry 4.0
Posted by Cosmin Bucur <co...@gmail.com>.
Thanks Mb ,
for upgrading the documentation and clarifying the issue for me . I
now understand that it's action I should have been using , and indeed
, I am wrong when saying this is a bug at all .
I did come from Tapestry 3.0 and in the chaos of upgrading my app from
Tap 3 to Tap 4 ( and hib 3 from hib 2 ) , I have overlooked the action
parameter since I was really adressing stuff that wasn't working
anymore .
So in the end I appologise for the noise , allthough i'm glad to see ,
that steps have been taken for this issue to become less confusing .
cosmin
On 2/8/06, Mind Bridge <mi...@yahoo.com> wrote:
> Hi Cosmin,
>
> Because of the problems that you have encountered, the documentation of
> the Submit, ImageSubmit, and LinkSubmit components has now been modified
> to be more explicit and understandable. Hopefully the modifications will
> avoid similar issues in the future. The changes will be applied next
> time when Howard updates the site.
>
> Nevertheless, consider the following:
> - All of the examples in the T4 documentation use 'action' rather than
> 'listener'
> - 'action' has been clearly described in the Submit component
> documentation ("A listener that is notified if this component is
> triggered just before the form's listener, after all components enclosed
> by the Form have had a chance to update their properties."). The
> explanation is now better, but I believe the above is still clear.
> - The difference between 'listener' and 'action' has been discussed in
> the component description.
> - 'listener' had exactly the same behavior in T3. Changing that has led
> to a number of backward compatibility problems and other misunderstandings
> - The immediate invocation of 'listener' is badly needed in loops (or
> tables, etc) and cannot be eliminated
> - A number of other UI systems use precisely 'action' to identify a
> listener with such an invocation.
>
> Best regards,
> -mb
>
>
> Cosmin Bucur wrote:
> > Guys ,
> >
> > I know nobody's getting paid to do this , and i'll repeat it , i am in
> > no way trying to put anybody or anything down . Or to complain for
> > that matter . Beeing mad because I've lost a day troubleshooting my
> > code not knowing about this , is not an issue , considering Tapestry's
> > saved me so much time with other issues . I am simply providing
> > constructing criticism trying to improve the image of tapestry when
> > faced with newcomers eager to become productive with a short and easy
> > learning curve .
> >
> > However I do consider it a severe problem . Why ? Because if you try
> > to have a @Submit outside of a form , you get an error . Which leads
> > you to believe even more that a tapestry form is exactly what it
> > should be , a wrapper arround a regular form that submits all it's
> > enclosing fields on it once it's posted . This will confuse people .
> >
> > As for improving the documentation ... what do I need to do ? The only
> > thig i can sugest is a big red banner ON TOP of the page that
> > describes the @Form and @Submit components , to make sure that people
> > will know that it won't work how one would logically anticipate , or
> > how one is used traditionally from http / html .
> >
> > I have not tried the action parameter yet , my forms were positioned
> > absolute , so I simply moved the Submit at the end , which works .
> >
> >
> > On 2/8/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> >
> >> Cosmin:
> >>
> >> This is a volunteer project. We're not giving paid support or anything,
> >> so we depend on user contribution to fix these kinds of unexpected
> >> behavior.
> >>
> >> Now, in respect to this issue: This is not a bug. Not a code bug, at
> >> least, as it is documented and it's expected behavior. I agree with you
> >> that it is unexpected behaviour and that it should be more prominent for
> >> new users, and that the old behavior should be deprecated. But it's not
> >> a "severe bug". Rather, I ask you to help improve this documentation ;).
> >>
> >> Did the "action" parameter work for you?
> >>
> >> --
> >> Ing. Leonardo Quijano Vincenzi
> >> DTQ Software
> >>
> >>
> >> Cosmin Bucur wrote:
> >>
> >>> Geoff , in html when writting a form , it doesn't matter where you put
> >>> your submit , everything that's in that form gets posted with the form
> >>> . Tapestry is the one framework that lets you code html rather than
> >>> wierd tags . So the more the reason for someone to asume that it will
> >>> work just like regular html . When starting with Tapestry , that's the
> >>> last thing i'd be looking for in the docs . But it's not about me ,
> >>> now i know i've had a problem it's about the others that will and have
> >>> ran into this problem . The bug is not in tacos , and in fact I
> >>> brought up the issue there first , I've mentioned this in my first
> >>> message .
> >>>
> >>> Jesse , tapestry is an amazing framework , it's the only thing I use
> >>> nowadays for web stuff . I am not trying to put tapestry down or it's
> >>> coders , however I am definently disagreeing with leaving landmines
> >>> throughout a final release just to make sure that every single line of
> >>> documentation is read . Things like theese steepen the learning curve
> >>> and will make new comers fall and break their ... code ... in a more
> >>> direct sencence : will keep potential users away , then we can all
> >>> wonder about how good Tapestry is and how much less it's used in
> >>> comparation with other inferior main stream frameworks .
> >>>
> >>> On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
> >>>
> >>>
> >>>> ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
> >>>> are you calling this a bug? It's explicity outlined in the
> >>>> ComponentReference for Submit that a 'listener' is triggered as the
> >>>> form is rewound and an 'action' is triggered just before the
> >>>> formlistener and after all the other form components have been
> >>>> rewound.
> >>>>
> >>>> is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
> >>>> and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
> >>>> and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
> >>>> the tacos documentation states that they adhere to the
> >>>> Submit/LinkSubmit semantics?
> >>>>
> >>>> If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
> >>>> bug in Tapestry, it's a bug in tacos and this is subject for the tacos
> >>>> mailing list.
> >>>>
> >>>>
> >>>>
> >>>> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> >>>>
> >>>>
> >>>>> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> >>>>> Submit I guess . Sorry to say this , but known behaviour or not , I
> >>>>> can't belive a final would be released with such a surprise bug . So
> >>>>> if you havn't worn out everysingle corner of documentation , and you
> >>>>> stubmle across something like this u're screwed ...
> >>>>>
> >>>>> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> >>>>>
> >>>>>
> >>>>>> I think it's either a linksubmit or submit. He may have better luck using
> >>>>>> the "action" binding instead of the listener , but it's too fuzzy in my had
> >>>>>> right now to be sure.
> >>>>>>
> >>>>>> On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>>> What is save? a Submit? a link?
> >>>>>>>
> >>>>>>> Geoff
> >>>>>>>
> >>>>>>> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>> Isn't this known Tapestry behavior?
> >>>>>>>> I'm assuming your "save" component is some kind of DirectLink with a
> >>>>>>>> "listener" parameter. You can try using the "action" parameter instead.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Ing. Leonardo Quijano Vincenzi
> >>>>>>>> DTQ Software
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Cosmin Bucur wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> I have initially reported this to Tacos , since that's what I'm using
> >>>>>>>>> , but then it was confirmed that the problem also shows up in Tapestry
> >>>>>>>>> without tacos .
> >>>>>>>>>
> >>>>>>>>> Basically if you have a form :
> >>>>>>>>>
> >>>>>>>>> <form jwcid="@Form">
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> <span jwcid="field1" />
> >>>>>>>>> <a jwcid="save">Save</a>
> >>>>>>>>> <span jwcid="field2" />
> >>>>>>>>>
> >>>>>>>>> </form>
> >>>>>>>>>
> >>>>>>>>> Only the fields before the save link get submited , the rest are
> >>>>>>>>> ignored , and not saved to the data obj .
> >>>>>>>>>
> >>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>> 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
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>> --
> >>>>>>> The Spindle guy. http://spindle.sf.net
> >>>>>>> Get help with Spindle:
> >>>>>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> >>>>>>> Blog: http://jroller.com/page/glongman
> >>>>>>> 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
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>> --
> >>>> The Spindle guy. http://spindle.sf.net
> >>>> Get help with Spindle:
> >>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> >>>> Blog: http://jroller.com/page/glongman
> >>>> 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
> >>>
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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: Severe Form bug in tapestry 4.0
Posted by Mind Bridge <mi...@yahoo.com>.
Hi Cosmin,
Because of the problems that you have encountered, the documentation of
the Submit, ImageSubmit, and LinkSubmit components has now been modified
to be more explicit and understandable. Hopefully the modifications will
avoid similar issues in the future. The changes will be applied next
time when Howard updates the site.
Nevertheless, consider the following:
- All of the examples in the T4 documentation use 'action' rather than
'listener'
- 'action' has been clearly described in the Submit component
documentation ("A listener that is notified if this component is
triggered just before the form's listener, after all components enclosed
by the Form have had a chance to update their properties."). The
explanation is now better, but I believe the above is still clear.
- The difference between 'listener' and 'action' has been discussed in
the component description.
- 'listener' had exactly the same behavior in T3. Changing that has led
to a number of backward compatibility problems and other misunderstandings
- The immediate invocation of 'listener' is badly needed in loops (or
tables, etc) and cannot be eliminated
- A number of other UI systems use precisely 'action' to identify a
listener with such an invocation.
Best regards,
-mb
Cosmin Bucur wrote:
> Guys ,
>
> I know nobody's getting paid to do this , and i'll repeat it , i am in
> no way trying to put anybody or anything down . Or to complain for
> that matter . Beeing mad because I've lost a day troubleshooting my
> code not knowing about this , is not an issue , considering Tapestry's
> saved me so much time with other issues . I am simply providing
> constructing criticism trying to improve the image of tapestry when
> faced with newcomers eager to become productive with a short and easy
> learning curve .
>
> However I do consider it a severe problem . Why ? Because if you try
> to have a @Submit outside of a form , you get an error . Which leads
> you to believe even more that a tapestry form is exactly what it
> should be , a wrapper arround a regular form that submits all it's
> enclosing fields on it once it's posted . This will confuse people .
>
> As for improving the documentation ... what do I need to do ? The only
> thig i can sugest is a big red banner ON TOP of the page that
> describes the @Form and @Submit components , to make sure that people
> will know that it won't work how one would logically anticipate , or
> how one is used traditionally from http / html .
>
> I have not tried the action parameter yet , my forms were positioned
> absolute , so I simply moved the Submit at the end , which works .
>
>
> On 2/8/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
>
>> Cosmin:
>>
>> This is a volunteer project. We're not giving paid support or anything,
>> so we depend on user contribution to fix these kinds of unexpected
>> behavior.
>>
>> Now, in respect to this issue: This is not a bug. Not a code bug, at
>> least, as it is documented and it's expected behavior. I agree with you
>> that it is unexpected behaviour and that it should be more prominent for
>> new users, and that the old behavior should be deprecated. But it's not
>> a "severe bug". Rather, I ask you to help improve this documentation ;).
>>
>> Did the "action" parameter work for you?
>>
>> --
>> Ing. Leonardo Quijano Vincenzi
>> DTQ Software
>>
>>
>> Cosmin Bucur wrote:
>>
>>> Geoff , in html when writting a form , it doesn't matter where you put
>>> your submit , everything that's in that form gets posted with the form
>>> . Tapestry is the one framework that lets you code html rather than
>>> wierd tags . So the more the reason for someone to asume that it will
>>> work just like regular html . When starting with Tapestry , that's the
>>> last thing i'd be looking for in the docs . But it's not about me ,
>>> now i know i've had a problem it's about the others that will and have
>>> ran into this problem . The bug is not in tacos , and in fact I
>>> brought up the issue there first , I've mentioned this in my first
>>> message .
>>>
>>> Jesse , tapestry is an amazing framework , it's the only thing I use
>>> nowadays for web stuff . I am not trying to put tapestry down or it's
>>> coders , however I am definently disagreeing with leaving landmines
>>> throughout a final release just to make sure that every single line of
>>> documentation is read . Things like theese steepen the learning curve
>>> and will make new comers fall and break their ... code ... in a more
>>> direct sencence : will keep potential users away , then we can all
>>> wonder about how good Tapestry is and how much less it's used in
>>> comparation with other inferior main stream frameworks .
>>>
>>> On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
>>>
>>>
>>>> ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
>>>> are you calling this a bug? It's explicity outlined in the
>>>> ComponentReference for Submit that a 'listener' is triggered as the
>>>> form is rewound and an 'action' is triggered just before the
>>>> formlistener and after all the other form components have been
>>>> rewound.
>>>>
>>>> is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
>>>> and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
>>>> and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
>>>> the tacos documentation states that they adhere to the
>>>> Submit/LinkSubmit semantics?
>>>>
>>>> If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
>>>> bug in Tapestry, it's a bug in tacos and this is subject for the tacos
>>>> mailing list.
>>>>
>>>>
>>>>
>>>> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
>>>>
>>>>
>>>>> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
>>>>> Submit I guess . Sorry to say this , but known behaviour or not , I
>>>>> can't belive a final would be released with such a surprise bug . So
>>>>> if you havn't worn out everysingle corner of documentation , and you
>>>>> stubmle across something like this u're screwed ...
>>>>>
>>>>> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>> I think it's either a linksubmit or submit. He may have better luck using
>>>>>> the "action" binding instead of the listener , but it's too fuzzy in my had
>>>>>> right now to be sure.
>>>>>>
>>>>>> On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>> What is save? a Submit? a link?
>>>>>>>
>>>>>>> Geoff
>>>>>>>
>>>>>>> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Isn't this known Tapestry behavior?
>>>>>>>> I'm assuming your "save" component is some kind of DirectLink with a
>>>>>>>> "listener" parameter. You can try using the "action" parameter instead.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Ing. Leonardo Quijano Vincenzi
>>>>>>>> DTQ Software
>>>>>>>>
>>>>>>>>
>>>>>>>> Cosmin Bucur wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> I have initially reported this to Tacos , since that's what I'm using
>>>>>>>>> , but then it was confirmed that the problem also shows up in Tapestry
>>>>>>>>> without tacos .
>>>>>>>>>
>>>>>>>>> Basically if you have a form :
>>>>>>>>>
>>>>>>>>> <form jwcid="@Form">
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <span jwcid="field1" />
>>>>>>>>> <a jwcid="save">Save</a>
>>>>>>>>> <span jwcid="field2" />
>>>>>>>>>
>>>>>>>>> </form>
>>>>>>>>>
>>>>>>>>> Only the fields before the save link get submited , the rest are
>>>>>>>>> ignored , and not saved to the data obj .
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> The Spindle guy. http://spindle.sf.net
>>>>>>> Get help with Spindle:
>>>>>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
>>>>>>> Blog: http://jroller.com/page/glongman
>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> The Spindle guy. http://spindle.sf.net
>>>> Get help with Spindle:
>>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
>>>> Blog: http://jroller.com/page/glongman
>>>> 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
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Severe Form bug in tapestry 4.0
Posted by Cosmin Bucur <co...@gmail.com>.
Guys ,
I know nobody's getting paid to do this , and i'll repeat it , i am in
no way trying to put anybody or anything down . Or to complain for
that matter . Beeing mad because I've lost a day troubleshooting my
code not knowing about this , is not an issue , considering Tapestry's
saved me so much time with other issues . I am simply providing
constructing criticism trying to improve the image of tapestry when
faced with newcomers eager to become productive with a short and easy
learning curve .
However I do consider it a severe problem . Why ? Because if you try
to have a @Submit outside of a form , you get an error . Which leads
you to believe even more that a tapestry form is exactly what it
should be , a wrapper arround a regular form that submits all it's
enclosing fields on it once it's posted . This will confuse people .
As for improving the documentation ... what do I need to do ? The only
thig i can sugest is a big red banner ON TOP of the page that
describes the @Form and @Submit components , to make sure that people
will know that it won't work how one would logically anticipate , or
how one is used traditionally from http / html .
I have not tried the action parameter yet , my forms were positioned
absolute , so I simply moved the Submit at the end , which works .
On 2/8/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> Cosmin:
>
> This is a volunteer project. We're not giving paid support or anything,
> so we depend on user contribution to fix these kinds of unexpected
> behavior.
>
> Now, in respect to this issue: This is not a bug. Not a code bug, at
> least, as it is documented and it's expected behavior. I agree with you
> that it is unexpected behaviour and that it should be more prominent for
> new users, and that the old behavior should be deprecated. But it's not
> a "severe bug". Rather, I ask you to help improve this documentation ;).
>
> Did the "action" parameter work for you?
>
> --
> Ing. Leonardo Quijano Vincenzi
> DTQ Software
>
>
> Cosmin Bucur wrote:
> > Geoff , in html when writting a form , it doesn't matter where you put
> > your submit , everything that's in that form gets posted with the form
> > . Tapestry is the one framework that lets you code html rather than
> > wierd tags . So the more the reason for someone to asume that it will
> > work just like regular html . When starting with Tapestry , that's the
> > last thing i'd be looking for in the docs . But it's not about me ,
> > now i know i've had a problem it's about the others that will and have
> > ran into this problem . The bug is not in tacos , and in fact I
> > brought up the issue there first , I've mentioned this in my first
> > message .
> >
> > Jesse , tapestry is an amazing framework , it's the only thing I use
> > nowadays for web stuff . I am not trying to put tapestry down or it's
> > coders , however I am definently disagreeing with leaving landmines
> > throughout a final release just to make sure that every single line of
> > documentation is read . Things like theese steepen the learning curve
> > and will make new comers fall and break their ... code ... in a more
> > direct sencence : will keep potential users away , then we can all
> > wonder about how good Tapestry is and how much less it's used in
> > comparation with other inferior main stream frameworks .
> >
> > On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
> >
> >> ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
> >> are you calling this a bug? It's explicity outlined in the
> >> ComponentReference for Submit that a 'listener' is triggered as the
> >> form is rewound and an 'action' is triggered just before the
> >> formlistener and after all the other form components have been
> >> rewound.
> >>
> >> is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
> >> and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
> >> and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
> >> the tacos documentation states that they adhere to the
> >> Submit/LinkSubmit semantics?
> >>
> >> If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
> >> bug in Tapestry, it's a bug in tacos and this is subject for the tacos
> >> mailing list.
> >>
> >>
> >>
> >> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> >>
> >>> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> >>> Submit I guess . Sorry to say this , but known behaviour or not , I
> >>> can't belive a final would be released with such a surprise bug . So
> >>> if you havn't worn out everysingle corner of documentation , and you
> >>> stubmle across something like this u're screwed ...
> >>>
> >>> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> >>>
> >>>> I think it's either a linksubmit or submit. He may have better luck using
> >>>> the "action" binding instead of the listener , but it's too fuzzy in my had
> >>>> right now to be sure.
> >>>>
> >>>> On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> >>>>
> >>>>> What is save? a Submit? a link?
> >>>>>
> >>>>> Geoff
> >>>>>
> >>>>> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> >>>>>
> >>>>>> Isn't this known Tapestry behavior?
> >>>>>> I'm assuming your "save" component is some kind of DirectLink with a
> >>>>>> "listener" parameter. You can try using the "action" parameter instead.
> >>>>>>
> >>>>>> --
> >>>>>> Ing. Leonardo Quijano Vincenzi
> >>>>>> DTQ Software
> >>>>>>
> >>>>>>
> >>>>>> Cosmin Bucur wrote:
> >>>>>>
> >>>>>>> I have initially reported this to Tacos , since that's what I'm using
> >>>>>>> , but then it was confirmed that the problem also shows up in Tapestry
> >>>>>>> without tacos .
> >>>>>>>
> >>>>>>> Basically if you have a form :
> >>>>>>>
> >>>>>>> <form jwcid="@Form">
> >>>>>>>
> >>>>>>>
> >>>>>>> <span jwcid="field1" />
> >>>>>>> <a jwcid="save">Save</a>
> >>>>>>> <span jwcid="field2" />
> >>>>>>>
> >>>>>>> </form>
> >>>>>>>
> >>>>>>> Only the fields before the save link get submited , the rest are
> >>>>>>> ignored , and not saved to the data obj .
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>> 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
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> --
> >>>>> The Spindle guy. http://spindle.sf.net
> >>>>> Get help with Spindle:
> >>>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> >>>>> Blog: http://jroller.com/page/glongman
> >>>>> 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
> >>>
> >>>
> >>>
> >> --
> >> The Spindle guy. http://spindle.sf.net
> >> Get help with Spindle:
> >> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> >> Blog: http://jroller.com/page/glongman
> >> 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
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> 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: Severe Form bug in tapestry 4.0
Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Cosmin:
This is a volunteer project. We're not giving paid support or anything,
so we depend on user contribution to fix these kinds of unexpected
behavior.
Now, in respect to this issue: This is not a bug. Not a code bug, at
least, as it is documented and it's expected behavior. I agree with you
that it is unexpected behaviour and that it should be more prominent for
new users, and that the old behavior should be deprecated. But it's not
a "severe bug". Rather, I ask you to help improve this documentation ;).
Did the "action" parameter work for you?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Cosmin Bucur wrote:
> Geoff , in html when writting a form , it doesn't matter where you put
> your submit , everything that's in that form gets posted with the form
> . Tapestry is the one framework that lets you code html rather than
> wierd tags . So the more the reason for someone to asume that it will
> work just like regular html . When starting with Tapestry , that's the
> last thing i'd be looking for in the docs . But it's not about me ,
> now i know i've had a problem it's about the others that will and have
> ran into this problem . The bug is not in tacos , and in fact I
> brought up the issue there first , I've mentioned this in my first
> message .
>
> Jesse , tapestry is an amazing framework , it's the only thing I use
> nowadays for web stuff . I am not trying to put tapestry down or it's
> coders , however I am definently disagreeing with leaving landmines
> throughout a final release just to make sure that every single line of
> documentation is read . Things like theese steepen the learning curve
> and will make new comers fall and break their ... code ... in a more
> direct sencence : will keep potential users away , then we can all
> wonder about how good Tapestry is and how much less it's used in
> comparation with other inferior main stream frameworks .
>
> On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
>
>> ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
>> are you calling this a bug? It's explicity outlined in the
>> ComponentReference for Submit that a 'listener' is triggered as the
>> form is rewound and an 'action' is triggered just before the
>> formlistener and after all the other form components have been
>> rewound.
>>
>> is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
>> and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
>> and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
>> the tacos documentation states that they adhere to the
>> Submit/LinkSubmit semantics?
>>
>> If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
>> bug in Tapestry, it's a bug in tacos and this is subject for the tacos
>> mailing list.
>>
>>
>>
>> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
>>
>>> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
>>> Submit I guess . Sorry to say this , but known behaviour or not , I
>>> can't belive a final would be released with such a surprise bug . So
>>> if you havn't worn out everysingle corner of documentation , and you
>>> stubmle across something like this u're screwed ...
>>>
>>> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>>>
>>>> I think it's either a linksubmit or submit. He may have better luck using
>>>> the "action" binding instead of the listener , but it's too fuzzy in my had
>>>> right now to be sure.
>>>>
>>>> On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
>>>>
>>>>> What is save? a Submit? a link?
>>>>>
>>>>> Geoff
>>>>>
>>>>> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
>>>>>
>>>>>> Isn't this known Tapestry behavior?
>>>>>> I'm assuming your "save" component is some kind of DirectLink with a
>>>>>> "listener" parameter. You can try using the "action" parameter instead.
>>>>>>
>>>>>> --
>>>>>> Ing. Leonardo Quijano Vincenzi
>>>>>> DTQ Software
>>>>>>
>>>>>>
>>>>>> Cosmin Bucur wrote:
>>>>>>
>>>>>>> I have initially reported this to Tacos , since that's what I'm using
>>>>>>> , but then it was confirmed that the problem also shows up in Tapestry
>>>>>>> without tacos .
>>>>>>>
>>>>>>> Basically if you have a form :
>>>>>>>
>>>>>>> <form jwcid="@Form">
>>>>>>>
>>>>>>>
>>>>>>> <span jwcid="field1" />
>>>>>>> <a jwcid="save">Save</a>
>>>>>>> <span jwcid="field2" />
>>>>>>>
>>>>>>> </form>
>>>>>>>
>>>>>>> Only the fields before the save link get submited , the rest are
>>>>>>> ignored , and not saved to the data obj .
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> The Spindle guy. http://spindle.sf.net
>>>>> Get help with Spindle:
>>>>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
>>>>> Blog: http://jroller.com/page/glongman
>>>>> 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
>>>
>>>
>>>
>> --
>> The Spindle guy. http://spindle.sf.net
>> Get help with Spindle:
>> http://lists.sourceforge.net/mailman/listinfo/spindle-user
>> Blog: http://jroller.com/page/glongman
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Severe Form bug in tapestry 4.0
Posted by Ron Piterman <rp...@gmx.net>.
Its defenitly not a bug but how things work.
The listener is called in the order of appearance, the action is called
"deferred", just before the form's listener.
The reason this seems to you a land-mine and is not documented in red is
because in tapestry 3.0 the listener was the only one there, so for
people who migrate from 3, and to the tapestry developers, this is very
well known. its obvious.
The docs might really miss one or other point, and a better work is
definetly needed on it (take a look at the contrib:table docu... *g* ) -
or rather, a better project *organisation*, and maybe this issue should
be addressed soon, as part of making tapestry an apache top project.
We did prospone the final release for a few weeks only because of
documentation lacks, but when it passed the final vote, no one had
raised his voice about that one -
In the scale of the tapestry project and in the present organisation of
the project, this will happen again and again...
Still, if you look around, there are no alternatives :)
Cheers,
Ron
Cosmin Bucur wrote:
> Geoff , in html when writting a form , it doesn't matter where you put
> your submit , everything that's in that form gets posted with the form
> . Tapestry is the one framework that lets you code html rather than
> wierd tags . So the more the reason for someone to asume that it will
> work just like regular html . When starting with Tapestry , that's the
> last thing i'd be looking for in the docs . But it's not about me ,
> now i know i've had a problem it's about the others that will and have
> ran into this problem . The bug is not in tacos , and in fact I
> brought up the issue there first , I've mentioned this in my first
> message .
>
> Jesse , tapestry is an amazing framework , it's the only thing I use
> nowadays for web stuff . I am not trying to put tapestry down or it's
> coders , however I am definently disagreeing with leaving landmines
> throughout a final release just to make sure that every single line of
> documentation is read . Things like theese steepen the learning curve
> and will make new comers fall and break their ... code ... in a more
> direct sencence : will keep potential users away , then we can all
> wonder about how good Tapestry is and how much less it's used in
> comparation with other inferior main stream frameworks .
>
> On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
>
>>ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
>>are you calling this a bug? It's explicity outlined in the
>>ComponentReference for Submit that a 'listener' is triggered as the
>>form is rewound and an 'action' is triggered just before the
>>formlistener and after all the other form components have been
>>rewound.
>>
>>is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
>>and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
>>and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
>>the tacos documentation states that they adhere to the
>>Submit/LinkSubmit semantics?
>>
>>If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
>>bug in Tapestry, it's a bug in tacos and this is subject for the tacos
>>mailing list.
>>
>>
>>
>>On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
>>
>>>I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
>>>Submit I guess . Sorry to say this , but known behaviour or not , I
>>>can't belive a final would be released with such a surprise bug . So
>>>if you havn't worn out everysingle corner of documentation , and you
>>>stubmle across something like this u're screwed ...
>>>
>>>On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>>>
>>>>I think it's either a linksubmit or submit. He may have better luck using
>>>>the "action" binding instead of the listener , but it's too fuzzy in my had
>>>>right now to be sure.
>>>>
>>>>On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
>>>>
>>>>>What is save? a Submit? a link?
>>>>>
>>>>>Geoff
>>>>>
>>>>>On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
>>>>>
>>>>>>Isn't this known Tapestry behavior?
>>>>>>I'm assuming your "save" component is some kind of DirectLink with a
>>>>>>"listener" parameter. You can try using the "action" parameter instead.
>>>>>>
>>>>>>--
>>>>>>Ing. Leonardo Quijano Vincenzi
>>>>>>DTQ Software
>>>>>>
>>>>>>
>>>>>>Cosmin Bucur wrote:
>>>>>>
>>>>>>>I have initially reported this to Tacos , since that's what I'm using
>>>>>>>, but then it was confirmed that the problem also shows up in Tapestry
>>>>>>>without tacos .
>>>>>>>
>>>>>>>Basically if you have a form :
>>>>>>>
>>>>>>><form jwcid="@Form">
>>>>>>>
>>>>>>>
>>>>>>> <span jwcid="field1" />
>>>>>>> <a jwcid="save">Save</a>
>>>>>>> <span jwcid="field2" />
>>>>>>>
>>>>>>> </form>
>>>>>>>
>>>>>>>Only the fields before the save link get submited , the rest are
>>>>>>>ignored , and not saved to the data obj .
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>The Spindle guy. http://spindle.sf.net
>>>>>Get help with Spindle:
>>>>>http://lists.sourceforge.net/mailman/listinfo/spindle-user
>>>>>Blog: http://jroller.com/page/glongman
>>>>>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
>>>
>>>
>>
>>
>>--
>>The Spindle guy. http://spindle.sf.net
>>Get help with Spindle:
>>http://lists.sourceforge.net/mailman/listinfo/spindle-user
>>Blog: http://jroller.com/page/glongman
>>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
Re: Severe Form bug in tapestry 4.0
Posted by Cosmin Bucur <co...@gmail.com>.
Geoff , in html when writting a form , it doesn't matter where you put
your submit , everything that's in that form gets posted with the form
. Tapestry is the one framework that lets you code html rather than
wierd tags . So the more the reason for someone to asume that it will
work just like regular html . When starting with Tapestry , that's the
last thing i'd be looking for in the docs . But it's not about me ,
now i know i've had a problem it's about the others that will and have
ran into this problem . The bug is not in tacos , and in fact I
brought up the issue there first , I've mentioned this in my first
message .
Jesse , tapestry is an amazing framework , it's the only thing I use
nowadays for web stuff . I am not trying to put tapestry down or it's
coders , however I am definently disagreeing with leaving landmines
throughout a final release just to make sure that every single line of
documentation is read . Things like theese steepen the learning curve
and will make new comers fall and break their ... code ... in a more
direct sencence : will keep potential users away , then we can all
wonder about how good Tapestry is and how much less it's used in
comparation with other inferior main stream frameworks .
On 2/8/06, Geoff Longman <gl...@gmail.com> wrote:
> ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
> are you calling this a bug? It's explicity outlined in the
> ComponentReference for Submit that a 'listener' is triggered as the
> form is rewound and an 'action' is triggered just before the
> formlistener and after all the other form components have been
> rewound.
>
> is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
> and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
> and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
> the tacos documentation states that they adhere to the
> Submit/LinkSubmit semantics?
>
> If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
> bug in Tapestry, it's a bug in tacos and this is subject for the tacos
> mailing list.
>
>
>
> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> > I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> > Submit I guess . Sorry to say this , but known behaviour or not , I
> > can't belive a final would be released with such a surprise bug . So
> > if you havn't worn out everysingle corner of documentation , and you
> > stubmle across something like this u're screwed ...
> >
> > On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > > I think it's either a linksubmit or submit. He may have better luck using
> > > the "action" binding instead of the listener , but it's too fuzzy in my had
> > > right now to be sure.
> > >
> > > On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> > > >
> > > > What is save? a Submit? a link?
> > > >
> > > > Geoff
> > > >
> > > > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > > > > Isn't this known Tapestry behavior?
> > > > > I'm assuming your "save" component is some kind of DirectLink with a
> > > > > "listener" parameter. You can try using the "action" parameter instead.
> > > > >
> > > > > --
> > > > > Ing. Leonardo Quijano Vincenzi
> > > > > DTQ Software
> > > > >
> > > > >
> > > > > Cosmin Bucur wrote:
> > > > > > I have initially reported this to Tacos , since that's what I'm using
> > > > > > , but then it was confirmed that the problem also shows up in Tapestry
> > > > > > without tacos .
> > > > > >
> > > > > > Basically if you have a form :
> > > > > >
> > > > > > <form jwcid="@Form">
> > > > > >
> > > > > >
> > > > > > <span jwcid="field1" />
> > > > > > <a jwcid="save">Save</a>
> > > > > > <span jwcid="field2" />
> > > > > >
> > > > > > </form>
> > > > > >
> > > > > > Only the fields before the save link get submited , the rest are
> > > > > > ignored , and not saved to the data obj .
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > The Spindle guy. http://spindle.sf.net
> > > > Get help with Spindle:
> > > > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > > > Blog: http://jroller.com/page/glongman
> > > > 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
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog: http://jroller.com/page/glongman
> 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
Re: Severe Form bug in tapestry 4.0
Posted by Geoff Longman <gl...@gmail.com>.
ok I don't know anything about AjaxSubmitLink and AjaxSubmit but why
are you calling this a bug? It's explicity outlined in the
ComponentReference for Submit that a 'listener' is triggered as the
form is rewound and an 'action' is triggered just before the
formlistener and after all the other form components have been
rewound.
is this a bug in the AjaxSubmitLink and AjaxSubmit? Are AjaxSubmitLink
and AjaxSubmit not adhering to the Submit contract?For AjaxSubmitLink
and AjaxSubmit, are the parameters the same as Submit/LinkSubmit and
the tacos documentation states that they adhere to the
Submit/LinkSubmit semantics?
If there is a problem with AjaxSubmitLink and AjaxSubmit it is not a
bug in Tapestry, it's a bug in tacos and this is subject for the tacos
mailing list.
On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> Submit I guess . Sorry to say this , but known behaviour or not , I
> can't belive a final would be released with such a surprise bug . So
> if you havn't worn out everysingle corner of documentation , and you
> stubmle across something like this u're screwed ...
>
> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > I think it's either a linksubmit or submit. He may have better luck using
> > the "action" binding instead of the listener , but it's too fuzzy in my had
> > right now to be sure.
> >
> > On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> > >
> > > What is save? a Submit? a link?
> > >
> > > Geoff
> > >
> > > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > > > Isn't this known Tapestry behavior?
> > > > I'm assuming your "save" component is some kind of DirectLink with a
> > > > "listener" parameter. You can try using the "action" parameter instead.
> > > >
> > > > --
> > > > Ing. Leonardo Quijano Vincenzi
> > > > DTQ Software
> > > >
> > > >
> > > > Cosmin Bucur wrote:
> > > > > I have initially reported this to Tacos , since that's what I'm using
> > > > > , but then it was confirmed that the problem also shows up in Tapestry
> > > > > without tacos .
> > > > >
> > > > > Basically if you have a form :
> > > > >
> > > > > <form jwcid="@Form">
> > > > >
> > > > >
> > > > > <span jwcid="field1" />
> > > > > <a jwcid="save">Save</a>
> > > > > <span jwcid="field2" />
> > > > >
> > > > > </form>
> > > > >
> > > > > Only the fields before the save link get submited , the rest are
> > > > > ignored , and not saved to the data obj .
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > The Spindle guy. http://spindle.sf.net
> > > Get help with Spindle:
> > > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > > Blog: http://jroller.com/page/glongman
> > > 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
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog: http://jroller.com/page/glongman
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: Severe Form bug in tapestry 4.0
Posted by Jesse Kuhnert <jk...@gmail.com>.
it's understandable to be mad, I was frustrated the first time I learned
about this as well, but it's hard to be all things to all people, esp. when
you are working for fun in your spare time. (ie priority list: fix feature
with code or document old feature with html/xml ? ) It's hard to find the
time sometimes.
If tapestry has ever made your day better in spite of the occasional bad
days, then it would seem reasonable to give something back once in a while.
On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
>
> then tapestry 4.0 should have been kept beta untill that was fixed ...
> anywais i don't want to stirr up ... ... but the reality is that i'm
> pissed because i've lost lots of time , and allthogh i'll get over
> that really soon ...
>
> it's hard to get over the fact that 4.0 is final with this behaviour :)
>
> you know , not all users roam the mlist ... how many users do you
> think might hit this problem and turn away from tapestry before asking
> any questions
>
>
>
> On 2/8/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > Very true.
> >
> > I'm probably going to find it hard to justify spending too many cycles
> on a
> > piece of functionality that I know will be going away (or should ) with
> the
> > next versio, but if someone wants to submit a documentation patch I'd be
> > grateful.
> >
> > jesse
> > On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> > >
> > > I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> > > Submit I guess . Sorry to say this , but known behaviour or not , I
> > > can't belive a final would be released with such a surprise bug . So
> > > if you havn't worn out everysingle corner of documentation , and you
> > > stubmle across something like this u're screwed ...
> > >
> > > On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > > > I think it's either a linksubmit or submit. He may have better luck
> > > using
> > > > the "action" binding instead of the listener , but it's too fuzzy in
> my
> > > had
> > > > right now to be sure.
> > > >
> > > > On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> > > > >
> > > > > What is save? a Submit? a link?
> > > > >
> > > > > Geoff
> > > > >
> > > > > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com>
> wrote:
> > > > > > Isn't this known Tapestry behavior?
> > > > > > I'm assuming your "save" component is some kind of DirectLink
> with a
> > > > > > "listener" parameter. You can try using the "action" parameter
> > > instead.
> > > > > >
> > > > > > --
> > > > > > Ing. Leonardo Quijano Vincenzi
> > > > > > DTQ Software
> > > > > >
> > > > > >
> > > > > > Cosmin Bucur wrote:
> > > > > > > I have initially reported this to Tacos , since that's what
> I'm
> > > using
> > > > > > > , but then it was confirmed that the problem also shows up in
> > > Tapestry
> > > > > > > without tacos .
> > > > > > >
> > > > > > > Basically if you have a form :
> > > > > > >
> > > > > > > <form jwcid="@Form">
> > > > > > >
> > > > > > >
> > > > > > > <span jwcid="field1" />
> > > > > > > <a jwcid="save">Save</a>
> > > > > > > <span jwcid="field2" />
> > > > > > >
> > > > > > > </form>
> > > > > > >
> > > > > > > Only the fields before the save link get submited , the rest
> are
> > > > > > > ignored , and not saved to the data obj .
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > The Spindle guy. http://spindle.sf.net
> > > > > Get help with Spindle:
> > > > > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > > > > Blog: http://jroller.com/page/glongman
> > > > > 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
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
Re: Severe Form bug in tapestry 4.0
Posted by Cosmin Bucur <co...@gmail.com>.
then tapestry 4.0 should have been kept beta untill that was fixed ...
anywais i don't want to stirr up ... ... but the reality is that i'm
pissed because i've lost lots of time , and allthogh i'll get over
that really soon ...
it's hard to get over the fact that 4.0 is final with this behaviour :)
you know , not all users roam the mlist ... how many users do you
think might hit this problem and turn away from tapestry before asking
any questions
On 2/8/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> Very true.
>
> I'm probably going to find it hard to justify spending too many cycles on a
> piece of functionality that I know will be going away (or should ) with the
> next versio, but if someone wants to submit a documentation patch I'd be
> grateful.
>
> jesse
> On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
> >
> > I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> > Submit I guess . Sorry to say this , but known behaviour or not , I
> > can't belive a final would be released with such a surprise bug . So
> > if you havn't worn out everysingle corner of documentation , and you
> > stubmle across something like this u're screwed ...
> >
> > On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > > I think it's either a linksubmit or submit. He may have better luck
> > using
> > > the "action" binding instead of the listener , but it's too fuzzy in my
> > had
> > > right now to be sure.
> > >
> > > On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> > > >
> > > > What is save? a Submit? a link?
> > > >
> > > > Geoff
> > > >
> > > > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > > > > Isn't this known Tapestry behavior?
> > > > > I'm assuming your "save" component is some kind of DirectLink with a
> > > > > "listener" parameter. You can try using the "action" parameter
> > instead.
> > > > >
> > > > > --
> > > > > Ing. Leonardo Quijano Vincenzi
> > > > > DTQ Software
> > > > >
> > > > >
> > > > > Cosmin Bucur wrote:
> > > > > > I have initially reported this to Tacos , since that's what I'm
> > using
> > > > > > , but then it was confirmed that the problem also shows up in
> > Tapestry
> > > > > > without tacos .
> > > > > >
> > > > > > Basically if you have a form :
> > > > > >
> > > > > > <form jwcid="@Form">
> > > > > >
> > > > > >
> > > > > > <span jwcid="field1" />
> > > > > > <a jwcid="save">Save</a>
> > > > > > <span jwcid="field2" />
> > > > > >
> > > > > > </form>
> > > > > >
> > > > > > Only the fields before the save link get submited , the rest are
> > > > > > ignored , and not saved to the data obj .
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > The Spindle guy. http://spindle.sf.net
> > > > Get help with Spindle:
> > > > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > > > Blog: http://jroller.com/page/glongman
> > > > 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
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Severe Form bug in tapestry 4.0
Posted by Jesse Kuhnert <jk...@gmail.com>.
Very true.
I'm probably going to find it hard to justify spending too many cycles on a
piece of functionality that I know will be going away (or should ) with the
next versio, but if someone wants to submit a documentation patch I'd be
grateful.
jesse
On 2/8/06, Cosmin Bucur <co...@gmail.com> wrote:
>
> I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
> Submit I guess . Sorry to say this , but known behaviour or not , I
> can't belive a final would be released with such a surprise bug . So
> if you havn't worn out everysingle corner of documentation , and you
> stubmle across something like this u're screwed ...
>
> On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > I think it's either a linksubmit or submit. He may have better luck
> using
> > the "action" binding instead of the listener , but it's too fuzzy in my
> had
> > right now to be sure.
> >
> > On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> > >
> > > What is save? a Submit? a link?
> > >
> > > Geoff
> > >
> > > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > > > Isn't this known Tapestry behavior?
> > > > I'm assuming your "save" component is some kind of DirectLink with a
> > > > "listener" parameter. You can try using the "action" parameter
> instead.
> > > >
> > > > --
> > > > Ing. Leonardo Quijano Vincenzi
> > > > DTQ Software
> > > >
> > > >
> > > > Cosmin Bucur wrote:
> > > > > I have initially reported this to Tacos , since that's what I'm
> using
> > > > > , but then it was confirmed that the problem also shows up in
> Tapestry
> > > > > without tacos .
> > > > >
> > > > > Basically if you have a form :
> > > > >
> > > > > <form jwcid="@Form">
> > > > >
> > > > >
> > > > > <span jwcid="field1" />
> > > > > <a jwcid="save">Save</a>
> > > > > <span jwcid="field2" />
> > > > >
> > > > > </form>
> > > > >
> > > > > Only the fields before the save link get submited , the rest are
> > > > > ignored , and not saved to the data obj .
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > The Spindle guy. http://spindle.sf.net
> > > Get help with Spindle:
> > > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > > Blog: http://jroller.com/page/glongman
> > > 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
>
>
Re: Severe Form bug in tapestry 4.0
Posted by Cosmin Bucur <co...@gmail.com>.
I was using AjaxSubmitLink and AjaxSubmit from tacos , which use
Submit I guess . Sorry to say this , but known behaviour or not , I
can't belive a final would be released with such a surprise bug . So
if you havn't worn out everysingle corner of documentation , and you
stubmle across something like this u're screwed ...
On 2/7/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> I think it's either a linksubmit or submit. He may have better luck using
> the "action" binding instead of the listener , but it's too fuzzy in my had
> right now to be sure.
>
> On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> >
> > What is save? a Submit? a link?
> >
> > Geoff
> >
> > On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > > Isn't this known Tapestry behavior?
> > > I'm assuming your "save" component is some kind of DirectLink with a
> > > "listener" parameter. You can try using the "action" parameter instead.
> > >
> > > --
> > > Ing. Leonardo Quijano Vincenzi
> > > DTQ Software
> > >
> > >
> > > Cosmin Bucur wrote:
> > > > I have initially reported this to Tacos , since that's what I'm using
> > > > , but then it was confirmed that the problem also shows up in Tapestry
> > > > without tacos .
> > > >
> > > > Basically if you have a form :
> > > >
> > > > <form jwcid="@Form">
> > > >
> > > >
> > > > <span jwcid="field1" />
> > > > <a jwcid="save">Save</a>
> > > > <span jwcid="field2" />
> > > >
> > > > </form>
> > > >
> > > > Only the fields before the save link get submited , the rest are
> > > > ignored , and not saved to the data obj .
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> >
> > --
> > The Spindle guy. http://spindle.sf.net
> > Get help with Spindle:
> > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > Blog: http://jroller.com/page/glongman
> > 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
Re: Severe Form bug in tapestry 4.0
Posted by Jesse Kuhnert <jk...@gmail.com>.
I think it's either a linksubmit or submit. He may have better luck using
the "action" binding instead of the listener , but it's too fuzzy in my had
right now to be sure.
On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
>
> What is save? a Submit? a link?
>
> Geoff
>
> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > Isn't this known Tapestry behavior?
> > I'm assuming your "save" component is some kind of DirectLink with a
> > "listener" parameter. You can try using the "action" parameter instead.
> >
> > --
> > Ing. Leonardo Quijano Vincenzi
> > DTQ Software
> >
> >
> > Cosmin Bucur wrote:
> > > I have initially reported this to Tacos , since that's what I'm using
> > > , but then it was confirmed that the problem also shows up in Tapestry
> > > without tacos .
> > >
> > > Basically if you have a form :
> > >
> > > <form jwcid="@Form">
> > >
> > >
> > > <span jwcid="field1" />
> > > <a jwcid="save">Save</a>
> > > <span jwcid="field2" />
> > >
> > > </form>
> > >
> > > Only the fields before the save link get submited , the rest are
> > > ignored , and not saved to the data obj .
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog: http://jroller.com/page/glongman
> 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: Severe Form bug in tapestry 4.0
Posted by Geoff Longman <gl...@gmail.com>.
Well I assume it's a submit with a name like save.
Leonardo is right, 'action' is probably what you want to bind the
listener to instead of 'listener'
Have a look at...
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/Submit.html
Geoff
On 2/7/06, Geoff Longman <gl...@gmail.com> wrote:
> What is save? a Submit? a link?
>
> Geoff
>
> On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> > Isn't this known Tapestry behavior?
> > I'm assuming your "save" component is some kind of DirectLink with a
> > "listener" parameter. You can try using the "action" parameter instead.
> >
> > --
> > Ing. Leonardo Quijano Vincenzi
> > DTQ Software
> >
> >
> > Cosmin Bucur wrote:
> > > I have initially reported this to Tacos , since that's what I'm using
> > > , but then it was confirmed that the problem also shows up in Tapestry
> > > without tacos .
> > >
> > > Basically if you have a form :
> > >
> > > <form jwcid="@Form">
> > >
> > >
> > > <span jwcid="field1" />
> > > <a jwcid="save">Save</a>
> > > <span jwcid="field2" />
> > >
> > > </form>
> > >
> > > Only the fields before the save link get submited , the rest are
> > > ignored , and not saved to the data obj .
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog: http://jroller.com/page/glongman
> 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
Blog: http://jroller.com/page/glongman
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: Severe Form bug in tapestry 4.0
Posted by Geoff Longman <gl...@gmail.com>.
What is save? a Submit? a link?
Geoff
On 2/7/06, Leonardo Quijano Vincenzi <le...@dtqsoftware.com> wrote:
> Isn't this known Tapestry behavior?
> I'm assuming your "save" component is some kind of DirectLink with a
> "listener" parameter. You can try using the "action" parameter instead.
>
> --
> Ing. Leonardo Quijano Vincenzi
> DTQ Software
>
>
> Cosmin Bucur wrote:
> > I have initially reported this to Tacos , since that's what I'm using
> > , but then it was confirmed that the problem also shows up in Tapestry
> > without tacos .
> >
> > Basically if you have a form :
> >
> > <form jwcid="@Form">
> >
> >
> > <span jwcid="field1" />
> > <a jwcid="save">Save</a>
> > <span jwcid="field2" />
> >
> > </form>
> >
> > Only the fields before the save link get submited , the rest are
> > ignored , and not saved to the data obj .
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog: http://jroller.com/page/glongman
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: Severe Form bug in tapestry 4.0
Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Isn't this known Tapestry behavior?
I'm assuming your "save" component is some kind of DirectLink with a
"listener" parameter. You can try using the "action" parameter instead.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Cosmin Bucur wrote:
> I have initially reported this to Tacos , since that's what I'm using
> , but then it was confirmed that the problem also shows up in Tapestry
> without tacos .
>
> Basically if you have a form :
>
> <form jwcid="@Form">
>
>
> <span jwcid="field1" />
> <a jwcid="save">Save</a>
> <span jwcid="field2" />
>
> </form>
>
> Only the fields before the save link get submited , the rest are
> ignored , and not saved to the data obj .
>
> ---------------------------------------------------------------------
> 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