Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

Hi Ernesto, We are fully aware of this! That's why the migration guide is split into "API breaks" and "Behavior changes". API breaks usually are easy to fix because the compiler complains about them. Behavior changes are not problem for Semantic Versioning but we postpone them to major versions

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

Tobias, > 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. > Mind that I'm fully aware of the personal sacrifices some people

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

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

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

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:

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

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

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. > >

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

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

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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:

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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 <

are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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? --

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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 !=

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

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",