Re: Prevent component markup regeneration in ajax call
Timo Rantalaiho escreveu: On Tue, 07 Oct 2008, Adriano dos Santos Fernandes wrote: So my question is how I could prevent wicket from regenerate the div when updating a component added to an AjaxRequestTarget? Not sure if this helps, but you can always add smaller parts inside your div to AjaxRequestTarget. Thanks for your comment. My problems was I has been generating javascript on the renderHead and the tag was being overwritten later. I solved it generating the javascript in onAfterRender for ajax calls. Adriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Prevent component markup regeneration in ajax call
On Tue, 07 Oct 2008, Adriano dos Santos Fernandes wrote: > So my question is how I could prevent wicket from regenerate the div > when updating a component added to an AjaxRequestTarget? Not sure if this helps, but you can always add smaller parts inside your div to AjaxRequestTarget. Best wishes, Timo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Prevent component markup regeneration in ajax call
Hi! I'd like to have extjs toolbar/menu working with Wicket ajax. What I want is, for example, in an ajax event show/hide menu items. I created the classes and the menu is rendered correctly. My toolbar render everything from its renderHead (IHeaderContributor) method. All javascript code is dumped to the response to render the ext component to a div. I looked at wicket-tools-extjs but still can't figure how to do what I need. If I re-render (ajax) the component it just hide. I tried different readerRead code when it's called by the second time, but the previously rendered component just hide too. So my question is how I could prevent wicket from regenerate the div when updating a component added to an AjaxRequestTarget? Adriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
