I don't see why having multiple ways to send information is reinventing the wheel. My point was that form submission is a standard for send information. Is the classic way. Ajax doesn't require this. You are able to send information on any javascript event. And maybe someone had implemented that.
I agree is simpler to have only one entry point. And has consistency, seems robust. Wicket triggers the same "conceptual" event, form submission. No matter how this is triggered, regular sumit or ajax. Finally, I will add the form component and send info using the standard way. Thanks! Juan On Wed, Apr 22, 2009 at 6:12 PM, Jeremy Thomerson <[email protected] > wrote: > Not really - I'd liken that to reinventing the wheel. Wicket provides > easy support for linking the component and the model through an ajax > event - form submission. But, you could probably write your own JS > that takes advantage of the wicket-ajax stuff and manually sends the > form values as parameters on the ajax request, etc... > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > > On Wed, Apr 22, 2009 at 4:06 PM, Juan G. Arias <[email protected]> > wrote: > > The html and the object component hierarchy would be simplier.My question > is > > why stay attached to the HTML standard (use forms to submit), if AJAX > > doesn't need to. > > > > I need this inside a form, and only for one or maybe two text fields. > > If I can link the component to the model without a form, I think it might > be > > better. > > > > Do you agree? > > > > On Wed, Apr 22, 2009 at 4:15 PM, Jeremy Thomerson < > [email protected] > >> wrote: > > > >> Why do you want an alternate way? Is there some advantage you see? > >> > >> -- > >> Jeremy Thomerson > >> http://www.wickettraining.com > >> > >> > >> > >> > >> On Wed, Apr 22, 2009 at 2:10 PM, Juan G. Arias <[email protected]> > >> wrote: > >> > Hi all,I wanted to check with you if my reasoning is ok. > >> > > >> > I have my model object, bound to some controls displayed in the page > >> using > >> > PropertyModel. > >> > I also have one ajax event (using a simple AjaxLink). > >> > > >> > When the user clicks this ajax link, some components in the page are > >> added > >> > to the ajax target in order to be updated. > >> > And the components linked to my model object resets to their original > >> > values. > >> > > >> > This is happening because there is no submission of information from > >> > browser, that's ok. > >> > > >> > One possible solution to this is to add a form component, surrounding > my > >> > components. And replace the AjaxLink with a AjaxSubmitLink. > >> > That would submit information from the form in the browser, update my > >> model, > >> > and finally render the components updated. > >> > > >> > Finally, the question: Is there any other option to do this? Does > wicket > >> > have some component to send information via ajax without a form? > >> > > >> > Form submission is the regular way to send information from browser to > >> > server, in regular (no ajax) pages. > >> > I understand that AjaxSubmitLink doesn't submit the whole page, only > the > >> > form, and that's nice. > >> > But i wonder if there is some alternate way to link properties to > >> > components. > >> > > >> > Thanks in advance! > >> > Juan > >> > > >> > >> --------------------------------------------------------------------- > >> 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] > >
