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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
> > > >
> > > > What is save? a Submit? a link?
> > > >
> > > > Geoff
> > > >
> > > > On 2/7/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > 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: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to