@Lance: Thx ... I didn't though about testing the ajaxformloop even though the name was quite obvious :P
@Thiago: As for now, my main concern is to get the client and component id. As for now, I'm forcing client id to be equals to component id and I'm using my ComponentSupport (that is a bridge to my component ComponentResources) to get it in my plugin. I'm now thinking about setting request parameters containing those two ids. My JS already uses custom wrapper for ajax requests so i'll be able to add them quite quiclky. It'll be less quick for tapestry standard form :D 2014-11-04 22:17 GMT+01:00 Thiago H de Paula Figueiredo <[email protected]> : > On Tue, 04 Nov 2014 18:13:15 -0200, Charlouze <[email protected]> wrote: > > @Thaigo: It has render things at page render and then it only >> communicates to the server via JS. >> > > I imagined that, but what needs to be done on these AJAX requests is what > defines how you should handle this situation. > > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
