Which model to use for forwarding form processing results?
Hi all, I have one and the same form on different pages used to provide some input data which is afterwards used by the form's onSubmit handler to request some complex data structure from a 3rd party service. This result needs to be forwarded to the caller/owner of the form, mainly pages, so those can provide the data to different views focussing on different aspects of the data. Most of those views are panels using different DataViews to provide data in HTML tables in the end. The important thing is that the form shouldn't render the results itself, only return some raw data structure, and the panels shouldn't need to know about the form as well. What is the best way to send those resulting data around? From my understanding it's not the default model of the form with all the convert input stuff, those input comes from the user, but it may be that of the page containing form and panels, so both could access the page and its default model. Else I could simply create a model instance and forward it using the CTORs of the form and panels, without (misusing?) the page's default model. Does it even matter at all? Thanks! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Hi Ernesto, I think as long as the third party library is not Wicket 7.0 proofed you should use it careful. Because of this the migration guide is very useful - each framework should be checked when upgrade a major version. Even on OS level there is a requirement note and sometimes API changes have impact on applications and their complete compatibility. kind regards Tobias > Am 09.05.2016 um 20:55 schrieb Ernesto Reinaldo Barreiro : > > Martin, > > Actually I was vaguely aware of having read the discussion related to the > issue... > > https://mail-archives.apache.org/mod_mbox/wicket-dev/201411.mbox/%3ccamomwmrvoeghovjj2u7pck9js2on-d28fww9fxck6xgyvcc...@mail.gmail.com%3E > > It was a bit more difficult to figure out this was the culprit in my case. > IMHO changes like these are "little changes" that might break applications > and leave users just wondering what's going on for a while... particularly > if your are using components integrating with third party JS libraries. > > > > On Mon, May 9, 2016 at 4:49 PM, Martin Grigorov > wrote: > >> >> https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.ajax.attributes.AjaxRequestAttributes#eventPropagationisnowBUBBLEbydefaultWICKET-5198 >> >> Having so detailed migration guide sometimes is a drawback - people don't >> want to read it completely :-) >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, May 9, 2016 at 4:23 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >>> Martin. >>> >>> Thanks for explanation. This little thing was preventing me from jumping >> to >>> wicket 7. Now I can migrate my project :-) >>> >>> On Mon, May 9, 2016 at 4:17 PM, Martin Grigorov >>> wrote: >>> On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Problem was >> attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > ); > > was need. Before STOP was the default, now it is BUBBLE. Just >> wondering > why default was changed? It changed because BUBBLE is the default in the browser DOM. > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: >> stripping bootstrap specifics makes wicket AJAX work. >> >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >>> @Martin, >>> >>> cleaned up working branch. >>> >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 >>> >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> Hi, Sorry for the long time it took... Today I finally managed to find some free time to create something you can use to see the problem in action: https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 Shows a component (Bootstrap radio choice) that does not work in wicket 7.3.0 and PR https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 shows the same component working on 6.3. [image: Inline image 1] @Martin, I will later on create a new (cleaner) PR to replace 603 to add >> only radio choice renderer for 6.x. Disclaimer: I do not know if this is an error introduced by the bootstrap layer or if this can be reproduced with a bare bones >>> wicket example. On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Let me see is I find the time to created it (it uses my own >>> bootstrap > components) > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier >>> wrote: > >> Hi, >> >> with a quickstart it would be easy to spot the problem. >> >> Regards >> Sven >> >> >>> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: >>> >>> Hi, >>> >>> >>> If I "revert" to 6.21.0 problem disappears so this seems to be >> a >>> 7.1.0 >>> "issue". >>> >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> >>> Well it is the same in the sense that no client side AJAX event seems to be triggered. On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: Hi Sven, > > Thanks for the feedback. It should not be the
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Martin, Actually I was vaguely aware of having read the discussion related to the issue... https://mail-archives.apache.org/mod_mbox/wicket-dev/201411.mbox/%3ccamomwmrvoeghovjj2u7pck9js2on-d28fww9fxck6xgyvcc...@mail.gmail.com%3E It was a bit more difficult to figure out this was the culprit in my case. IMHO changes like these are "little changes" that might break applications and leave users just wondering what's going on for a while... particularly if your are using components integrating with third party JS libraries. On Mon, May 9, 2016 at 4:49 PM, Martin Grigorov wrote: > > https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.ajax.attributes.AjaxRequestAttributes#eventPropagationisnowBUBBLEbydefaultWICKET-5198 > > Having so detailed migration guide sometimes is a drawback - people don't > want to read it completely :-) > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, May 9, 2016 at 4:23 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Martin. > > > > Thanks for explanation. This little thing was preventing me from jumping > to > > wicket 7. Now I can migrate my project :-) > > > > On Mon, May 9, 2016 at 4:17 PM, Martin Grigorov > > wrote: > > > > > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > Problem was > > > > > > > > > > > > > > attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > > > > ); > > > > > > > > was need. Before STOP was the default, now it is BUBBLE. Just > wondering > > > > why default was changed? > > > > > > > It changed because BUBBLE is the default in the browser DOM. > > > > > > > > > > > > > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > > > > reier...@gmail.com> wrote: > > > > > > > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: > > > >> stripping bootstrap specifics makes wicket AJAX work. > > > >> > > > >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < > > > >> reier...@gmail.com> wrote: > > > >> > > > >>> @Martin, > > > >>> > > > >>> cleaned up working branch. > > > >>> > > > >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 > > > >>> > > > >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < > > > >>> reier...@gmail.com> wrote: > > > >>> > > > Hi, > > > > > > Sorry for the long time it took... Today I finally managed to find > > > some > > > free time to create something you can use to see the problem in > > > action: > > > > > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 > > > > > > Shows a component (Bootstrap radio choice) that does not work in > > > wicket > > > 7.3.0 > > > > > > and PR > > > > > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 > > > > > > shows the same component working on 6.3. > > > > > > [image: Inline image 1] > > > > > > @Martin, > > > > > > I will later on create a new (cleaner) PR to replace 603 to add > only > > > radio choice renderer for 6.x. > > > > > > Disclaimer: I do not know if this is an error introduced by the > > > bootstrap layer or if this can be reproduced with a bare bones > > wicket > > > example. > > > > > > > > > On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > Let me see is I find the time to created it (it uses my own > > bootstrap > > > > components) > > > > > > > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier > > wrote: > > > > > > > >> Hi, > > > >> > > > >> with a quickstart it would be easy to spot the problem. > > > >> > > > >> Regards > > > >> Sven > > > >> > > > >> > > > >> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > > > >> > > > >>> Hi, > > > >>> > > > >>> > > > >>> If I "revert" to 6.21.0 problem disappears so this seems to be > a > > > >>> 7.1.0 > > > >>> "issue". > > > >>> > > > >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < > > > >>> reier...@gmail.com> wrote: > > > >>> > > > >>> Well it is the same in the sense that no client side AJAX event > > > seems to > > > be triggered. > > > > > > On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > Hi Sven, > > > > > > > > Thanks for the feedback. It should not be the case > > > > > > > > radioGroup = new RadioGroup("radioGroup", getModel()); > > > > tuneRadioGroup(radioGroup); > > > > radioGroup.setRenderBodyOnly(false); > > > > radioGroup.setOutputMarkupId(true); > > > > add(radioGroup); > > > >
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.ajax.attributes.AjaxRequestAttributes#eventPropagationisnowBUBBLEbydefaultWICKET-5198 Having so detailed migration guide sometimes is a drawback - people don't want to read it completely :-) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, May 9, 2016 at 4:23 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Martin. > > Thanks for explanation. This little thing was preventing me from jumping to > wicket 7. Now I can migrate my project :-) > > On Mon, May 9, 2016 at 4:17 PM, Martin Grigorov > wrote: > > > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > > Problem was > > > > > > > > > attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > > > ); > > > > > > was need. Before STOP was the default, now it is BUBBLE. Just wondering > > > why default was changed? > > > > > It changed because BUBBLE is the default in the browser DOM. > > > > > > > > > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: > > >> stripping bootstrap specifics makes wicket AJAX work. > > >> > > >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < > > >> reier...@gmail.com> wrote: > > >> > > >>> @Martin, > > >>> > > >>> cleaned up working branch. > > >>> > > >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 > > >>> > > >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < > > >>> reier...@gmail.com> wrote: > > >>> > > Hi, > > > > Sorry for the long time it took... Today I finally managed to find > > some > > free time to create something you can use to see the problem in > > action: > > > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 > > > > Shows a component (Bootstrap radio choice) that does not work in > > wicket > > 7.3.0 > > > > and PR > > > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 > > > > shows the same component working on 6.3. > > > > [image: Inline image 1] > > > > @Martin, > > > > I will later on create a new (cleaner) PR to replace 603 to add only > > radio choice renderer for 6.x. > > > > Disclaimer: I do not know if this is an error introduced by the > > bootstrap layer or if this can be reproduced with a bare bones > wicket > > example. > > > > > > On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > > Let me see is I find the time to created it (it uses my own > bootstrap > > > components) > > > > > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier > wrote: > > > > > >> Hi, > > >> > > >> with a quickstart it would be easy to spot the problem. > > >> > > >> Regards > > >> Sven > > >> > > >> > > >> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > > >> > > >>> Hi, > > >>> > > >>> > > >>> If I "revert" to 6.21.0 problem disappears so this seems to be a > > >>> 7.1.0 > > >>> "issue". > > >>> > > >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < > > >>> reier...@gmail.com> wrote: > > >>> > > >>> Well it is the same in the sense that no client side AJAX event > > seems to > > be triggered. > > > > On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > Hi Sven, > > > > > > Thanks for the feedback. It should not be the case > > > > > > radioGroup = new RadioGroup("radioGroup", getModel()); > > > tuneRadioGroup(radioGroup); > > > radioGroup.setRenderBodyOnly(false); > > > radioGroup.setOutputMarkupId(true); > > > add(radioGroup); > > > if(changeHandler != null) { > > > radioGroup.add(new > > > AjaxFormChoiceComponentUpdatingBehavior() { > > > > > > @Override > > > protected void onUpdate(AjaxRequestTarget > > target) > > > { > > > changeHandler.onSelectionChanged(target, > > > radioGroup.getModel().getObject()); > > > } > > > }); > > > } > > > > > > > > > > > > On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier > > > wrote: > > > > > > Hi, > > >> > > >> nothing specific I can think of ... perhaps WICKET-5476? > > >> > > >> Regards > > >> Sven > > >> > > >> > > >> On 17.11.2
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Martin. Thanks for explanation. This little thing was preventing me from jumping to wicket 7. Now I can migrate my project :-) On Mon, May 9, 2016 at 4:17 PM, Martin Grigorov wrote: > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Problem was > > > > > attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > > ); > > > > was need. Before STOP was the default, now it is BUBBLE. Just wondering > > why default was changed? > > > It changed because BUBBLE is the default in the browser DOM. > > > > > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: > >> stripping bootstrap specifics makes wicket AJAX work. > >> > >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < > >> reier...@gmail.com> wrote: > >> > >>> @Martin, > >>> > >>> cleaned up working branch. > >>> > >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 > >>> > >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < > >>> reier...@gmail.com> wrote: > >>> > Hi, > > Sorry for the long time it took... Today I finally managed to find > some > free time to create something you can use to see the problem in > action: > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 > > Shows a component (Bootstrap radio choice) that does not work in > wicket > 7.3.0 > > and PR > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 > > shows the same component working on 6.3. > > [image: Inline image 1] > > @Martin, > > I will later on create a new (cleaner) PR to replace 603 to add only > radio choice renderer for 6.x. > > Disclaimer: I do not know if this is an error introduced by the > bootstrap layer or if this can be reproduced with a bare bones wicket > example. > > > On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Let me see is I find the time to created it (it uses my own bootstrap > > components) > > > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: > > > >> Hi, > >> > >> with a quickstart it would be easy to spot the problem. > >> > >> Regards > >> Sven > >> > >> > >> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > >> > >>> Hi, > >>> > >>> > >>> If I "revert" to 6.21.0 problem disappears so this seems to be a > >>> 7.1.0 > >>> "issue". > >>> > >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < > >>> reier...@gmail.com> wrote: > >>> > >>> Well it is the same in the sense that no client side AJAX event > seems to > be triggered. > > On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > Hi Sven, > > > > Thanks for the feedback. It should not be the case > > > > radioGroup = new RadioGroup("radioGroup", getModel()); > > tuneRadioGroup(radioGroup); > > radioGroup.setRenderBodyOnly(false); > > radioGroup.setOutputMarkupId(true); > > add(radioGroup); > > if(changeHandler != null) { > > radioGroup.add(new > > AjaxFormChoiceComponentUpdatingBehavior() { > > > > @Override > > protected void onUpdate(AjaxRequestTarget > target) > > { > > changeHandler.onSelectionChanged(target, > > radioGroup.getModel().getObject()); > > } > > }); > > } > > > > > > > > On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier > > wrote: > > > > Hi, > >> > >> nothing specific I can think of ... perhaps WICKET-5476? > >> > >> Regards > >> Sven > >> > >> > >> On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: > >> > >> Hi, > >>> > >>> I have a bootstrap based component that uses a RadioGroup > >>> + AjaxFormChoiceComponentUpdatingBehavior. This was working > >>> perfectly > >>> fine > >>> on wicket 6. Now is no loger working with wicket 7. Are there > any > >>> (obvious) > >>> changes on the way RadioGroup works that might be preventing it > >>> from > >>> working? > >>> > >>> > >>> > >> > - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.ap
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Problem was > > attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > ); > > was need. Before STOP was the default, now it is BUBBLE. Just wondering > why default was changed? > It changed because BUBBLE is the default in the browser DOM. > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: >> stripping bootstrap specifics makes wicket AJAX work. >> >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >>> @Martin, >>> >>> cleaned up working branch. >>> >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 >>> >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> Hi, Sorry for the long time it took... Today I finally managed to find some free time to create something you can use to see the problem in action: https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 Shows a component (Bootstrap radio choice) that does not work in wicket 7.3.0 and PR https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 shows the same component working on 6.3. [image: Inline image 1] @Martin, I will later on create a new (cleaner) PR to replace 603 to add only radio choice renderer for 6.x. Disclaimer: I do not know if this is an error introduced by the bootstrap layer or if this can be reproduced with a bare bones wicket example. On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Let me see is I find the time to created it (it uses my own bootstrap > components) > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: > >> Hi, >> >> with a quickstart it would be easy to spot the problem. >> >> Regards >> Sven >> >> >> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: >> >>> Hi, >>> >>> >>> If I "revert" to 6.21.0 problem disappears so this seems to be a >>> 7.1.0 >>> "issue". >>> >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> >>> Well it is the same in the sense that no client side AJAX event seems to be triggered. On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: Hi Sven, > > Thanks for the feedback. It should not be the case > > radioGroup = new RadioGroup("radioGroup", getModel()); > tuneRadioGroup(radioGroup); > radioGroup.setRenderBodyOnly(false); > radioGroup.setOutputMarkupId(true); > add(radioGroup); > if(changeHandler != null) { > radioGroup.add(new > AjaxFormChoiceComponentUpdatingBehavior() { > > @Override > protected void onUpdate(AjaxRequestTarget target) > { > changeHandler.onSelectionChanged(target, > radioGroup.getModel().getObject()); > } > }); > } > > > > On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier > wrote: > > Hi, >> >> nothing specific I can think of ... perhaps WICKET-5476? >> >> Regards >> Sven >> >> >> On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: >> >> Hi, >>> >>> I have a bootstrap based component that uses a RadioGroup >>> + AjaxFormChoiceComponentUpdatingBehavior. This was working >>> perfectly >>> fine >>> on wicket 6. Now is no loger working with wicket 7. Are there any >>> (obvious) >>> changes on the way RadioGroup works that might be preventing it >>> from >>> working? >>> >>> >>> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > > -- Regards - Ernesto Reinaldo Barreiro >>> >>> >>> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- >
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Problem was attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP); was need. Before STOP was the default, now it is BUBBLE. Just wondering why default was changed? On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > This seem to be some bug on the bootstrap layer NOT a Wicket bug: > stripping bootstrap specifics makes wicket AJAX work. > > On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> @Martin, >> >> cleaned up working branch. >> >> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 >> >> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >>> Hi, >>> >>> Sorry for the long time it took... Today I finally managed to find some >>> free time to create something you can use to see the problem in action: >>> >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 >>> >>> Shows a component (Bootstrap radio choice) that does not work in wicket >>> 7.3.0 >>> >>> and PR >>> >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 >>> >>> shows the same component working on 6.3. >>> >>> [image: Inline image 1] >>> >>> @Martin, >>> >>> I will later on create a new (cleaner) PR to replace 603 to add only >>> radio choice renderer for 6.x. >>> >>> Disclaimer: I do not know if this is an error introduced by the >>> bootstrap layer or if this can be reproduced with a bare bones wicket >>> example. >>> >>> >>> On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> Let me see is I find the time to created it (it uses my own bootstrap components) On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: > Hi, > > with a quickstart it would be easy to spot the problem. > > Regards > Sven > > > On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > >> Hi, >> >> >> If I "revert" to 6.21.0 problem disappears so this seems to be a 7.1.0 >> "issue". >> >> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >> Well it is the same in the sense that no client side AJAX event seems >>> to >>> be triggered. >>> >>> On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> >>> Hi Sven, Thanks for the feedback. It should not be the case radioGroup = new RadioGroup("radioGroup", getModel()); tuneRadioGroup(radioGroup); radioGroup.setRenderBodyOnly(false); radioGroup.setOutputMarkupId(true); add(radioGroup); if(changeHandler != null) { radioGroup.add(new AjaxFormChoiceComponentUpdatingBehavior() { @Override protected void onUpdate(AjaxRequestTarget target) { changeHandler.onSelectionChanged(target, radioGroup.getModel().getObject()); } }); } On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier wrote: Hi, > > nothing specific I can think of ... perhaps WICKET-5476? > > Regards > Sven > > > On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: > > Hi, >> >> I have a bootstrap based component that uses a RadioGroup >> + AjaxFormChoiceComponentUpdatingBehavior. This was working >> perfectly >> fine >> on wicket 6. Now is no loger working with wicket 7. Are there any >> (obvious) >> changes on the way RadioGroup works that might be preventing it >> from >> working? >> >> >> > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- Regards - Ernesto Reinaldo Barreiro >>> >>> >>> -- >>> Regards - Ernesto Reinaldo Barreiro >>> >>> >> >> >> > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro >>> >>> >>> >>> -- >>> Regards - Ernesto Reinaldo Barreiro >>> >> >> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> > > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
This seem to be some bug on the bootstrap layer NOT a Wicket bug: stripping bootstrap specifics makes wicket AJAX work. On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > @Martin, > > cleaned up working branch. > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 > > On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> Hi, >> >> Sorry for the long time it took... Today I finally managed to find some >> free time to create something you can use to see the problem in action: >> >> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 >> >> Shows a component (Bootstrap radio choice) that does not work in wicket >> 7.3.0 >> >> and PR >> >> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 >> >> shows the same component working on 6.3. >> >> [image: Inline image 1] >> >> @Martin, >> >> I will later on create a new (cleaner) PR to replace 603 to add only >> radio choice renderer for 6.x. >> >> Disclaimer: I do not know if this is an error introduced by the bootstrap >> layer or if this can be reproduced with a bare bones wicket example. >> >> >> On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >>> Let me see is I find the time to created it (it uses my own bootstrap >>> components) >>> >>> On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: >>> Hi, with a quickstart it would be easy to spot the problem. Regards Sven On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > Hi, > > > If I "revert" to 6.21.0 problem disappears so this seems to be a 7.1.0 > "issue". > > On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > Well it is the same in the sense that no client side AJAX event seems >> to >> be triggered. >> >> On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >> Hi Sven, >>> >>> Thanks for the feedback. It should not be the case >>> >>> radioGroup = new RadioGroup("radioGroup", getModel()); >>> tuneRadioGroup(radioGroup); >>> radioGroup.setRenderBodyOnly(false); >>> radioGroup.setOutputMarkupId(true); >>> add(radioGroup); >>> if(changeHandler != null) { >>> radioGroup.add(new >>> AjaxFormChoiceComponentUpdatingBehavior() { >>> >>> @Override >>> protected void onUpdate(AjaxRequestTarget target) { >>> changeHandler.onSelectionChanged(target, >>> radioGroup.getModel().getObject()); >>> } >>> }); >>> } >>> >>> >>> >>> On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier wrote: >>> >>> Hi, nothing specific I can think of ... perhaps WICKET-5476? Regards Sven On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: Hi, > > I have a bootstrap based component that uses a RadioGroup > + AjaxFormChoiceComponentUpdatingBehavior. This was working > perfectly > fine > on wicket 6. Now is no loger working with wicket 7. Are there any > (obvious) > changes on the way RadioGroup works that might be preventing it > from > working? > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> -- >>> Regards - Ernesto Reinaldo Barreiro >>> >>> >> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> >> > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> -- >>> Regards - Ernesto Reinaldo Barreiro >>> >> >> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> > > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
@Martin, cleaned up working branch. https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > Sorry for the long time it took... Today I finally managed to find some > free time to create something you can use to see the problem in action: > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 > > Shows a component (Bootstrap radio choice) that does not work in wicket > 7.3.0 > > and PR > > https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 > > shows the same component working on 6.3. > > [image: Inline image 1] > > @Martin, > > I will later on create a new (cleaner) PR to replace 603 to add only radio > choice renderer for 6.x. > > Disclaimer: I do not know if this is an error introduced by the bootstrap > layer or if this can be reproduced with a bare bones wicket example. > > > On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> Let me see is I find the time to created it (it uses my own bootstrap >> components) >> >> On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: >> >>> Hi, >>> >>> with a quickstart it would be easy to spot the problem. >>> >>> Regards >>> Sven >>> >>> >>> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: >>> Hi, If I "revert" to 6.21.0 problem disappears so this seems to be a 7.1.0 "issue". On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: Well it is the same in the sense that no client side AJAX event seems to > be triggered. > > On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > Hi Sven, >> >> Thanks for the feedback. It should not be the case >> >> radioGroup = new RadioGroup("radioGroup", getModel()); >> tuneRadioGroup(radioGroup); >> radioGroup.setRenderBodyOnly(false); >> radioGroup.setOutputMarkupId(true); >> add(radioGroup); >> if(changeHandler != null) { >> radioGroup.add(new >> AjaxFormChoiceComponentUpdatingBehavior() { >> >> @Override >> protected void onUpdate(AjaxRequestTarget target) { >> changeHandler.onSelectionChanged(target, >> radioGroup.getModel().getObject()); >> } >> }); >> } >> >> >> >> On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier wrote: >> >> Hi, >>> >>> nothing specific I can think of ... perhaps WICKET-5476? >>> >>> Regards >>> Sven >>> >>> >>> On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: >>> >>> Hi, I have a bootstrap based component that uses a RadioGroup + AjaxFormChoiceComponentUpdatingBehavior. This was working perfectly fine on wicket 6. Now is no loger working with wicket 7. Are there any (obvious) changes on the way RadioGroup works that might be preventing it from working? >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> >> > > > -- > Regards - Ernesto Reinaldo Barreiro > > >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> > > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Hi, Sorry for the long time it took... Today I finally managed to find some free time to create something you can use to see the problem in action: https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 Shows a component (Bootstrap radio choice) that does not work in wicket 7.3.0 and PR https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 shows the same component working on 6.3. [image: Inline image 1] @Martin, I will later on create a new (cleaner) PR to replace 603 to add only radio choice renderer for 6.x. Disclaimer: I do not know if this is an error introduced by the bootstrap layer or if this can be reproduced with a bare bones wicket example. On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Let me see is I find the time to created it (it uses my own bootstrap > components) > > On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier wrote: > >> Hi, >> >> with a quickstart it would be easy to spot the problem. >> >> Regards >> Sven >> >> >> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: >> >>> Hi, >>> >>> >>> If I "revert" to 6.21.0 problem disappears so this seems to be a 7.1.0 >>> "issue". >>> >>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < >>> reier...@gmail.com> wrote: >>> >>> Well it is the same in the sense that no client side AJAX event seems to be triggered. On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: Hi Sven, > > Thanks for the feedback. It should not be the case > > radioGroup = new RadioGroup("radioGroup", getModel()); > tuneRadioGroup(radioGroup); > radioGroup.setRenderBodyOnly(false); > radioGroup.setOutputMarkupId(true); > add(radioGroup); > if(changeHandler != null) { > radioGroup.add(new > AjaxFormChoiceComponentUpdatingBehavior() { > > @Override > protected void onUpdate(AjaxRequestTarget target) { > changeHandler.onSelectionChanged(target, > radioGroup.getModel().getObject()); > } > }); > } > > > > On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier wrote: > > Hi, >> >> nothing specific I can think of ... perhaps WICKET-5476? >> >> Regards >> Sven >> >> >> On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: >> >> Hi, >>> >>> I have a bootstrap based component that uses a RadioGroup >>> + AjaxFormChoiceComponentUpdatingBehavior. This was working perfectly >>> fine >>> on wicket 6. Now is no loger working with wicket 7. Are there any >>> (obvious) >>> changes on the way RadioGroup works that might be preventing it from >>> working? >>> >>> >>> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > > -- Regards - Ernesto Reinaldo Barreiro >>> >>> >>> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNONCE] Wicket jQuery UI 7.3.0 released
Thanks a lot Sebastien! On Mon, May 9, 2016 at 4:24 PM, Sebastien wrote: > Dear Wicket jQuery & Kendo UI users, > > Wicket jQuery UI 7.3.0 based on Apache Wicket 7.3.0 is now released. > > *Changelog:* > > > https://github.com/sebfz1/wicket-jquery-ui/releases/tag/wicket-jquery-ui-7.3.0 > > *Maven dependencies* > > > > > com.googlecode.wicket-jquery-ui > wicket-jquery-ui > 7.3.0 > > > > > > com.googlecode.wicket-jquery-ui > wicket-kendo-ui > 7.3.0 > > > If you have any *question*, feel free to ask in the forum: > http://groups.google.com/group/wicket-jquery-ui/ > > If you notice an *issue*, please report it here: > https://github.com/sebfz1/wicket-jquery-ui/issues > > Enjoy! :) > Sebastien. > -- WBR Maxim aka solomax
[ANNONCE] Wicket jQuery UI 6.23.0 released
Dear Wicket jQuery & Kendo UI users, Wicket jQuery UI 6.23.0 based on Apache Wicket 6.23.0 is now released. *Changelog* (same as 7.3.0) https://github.com/sebfz1/wicket-jquery-ui/releases/tag/wicket-jquery-ui-7.3.0 *Maven dependencies* com.googlecode.wicket-jquery-ui wicket-jquery-ui 6.23.0 com.googlecode.wicket-jquery-ui wicket-kendo-ui 6.23.0 If you have any *question*, feel free to ask in the forum: http://groups.google.com/group/wicket-jquery-ui/ If you notice an *issue*, please report it here: https://github.com/sebfz1/wicket-jquery-ui/issues Enjoy! :) Sebastien.
[ANNONCE] Wicket jQuery UI 7.3.0 released
Dear Wicket jQuery & Kendo UI users, Wicket jQuery UI 7.3.0 based on Apache Wicket 7.3.0 is now released. *Changelog:* https://github.com/sebfz1/wicket-jquery-ui/releases/tag/wicket-jquery-ui-7.3.0 *Maven dependencies* com.googlecode.wicket-jquery-ui wicket-jquery-ui 7.3.0 com.googlecode.wicket-jquery-ui wicket-kendo-ui 7.3.0 If you have any *question*, feel free to ask in the forum: http://groups.google.com/group/wicket-jquery-ui/ If you notice an *issue*, please report it here: https://github.com/sebfz1/wicket-jquery-ui/issues Enjoy! :) Sebastien.