You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ernesto Reinaldo Barreiro <re...@gmail.com> on 2015/11/17 18:55:59 UTC
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?
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Martin Grigorov <mg...@apache.org>.
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 because of what you have said below - they are
silent and more hard to be debugged.
For all of them there is a respective discussion thread at dev@ - whether,
when and how to do them.
I know that most people are busy with their own business and family (me
included!) and don't have time to participate in discussions,
brainstorming, testing but this process is the best we can do at the
moment.
Any ideas for improving the process are always welcome!
I hope that we will release 8.0.0-M1 soon so more people like you can give
it a try and report issues and ideas for improvements before we freeze the
code for API breaks.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, May 10, 2016 at 9:32 AM, Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:
> 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 make to
> deliver new versions and improve the framework. So, what I tell bellow is
> with full respect to that.
>
> I'm NOT really "complaining" let's say I'm just voicing some concerns from
> users. This is the second Wicket application I migrate to Wicket 7.0 in
> last two of months. First application was for a customer and we encountered
> a few little "surprises", e.g.
>
>
> https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.markup.html.panel.FeedbackPanelDonotsetCSSclassontheli
> >spanelementforafeedbackmessageWICKET-4831
>
> IMHO changes like this bring no real value and just make migrations less
> "stable". Not to mention things like this
>
>
> https://ci.apache.org/projects/wicket/guide/7.x/guide/componentQueueing.html
>
> which might have made framework slower (according to certain post on
> list). I know that without changes there is no evolution. I'm just telling
> that maybe there is a need to make changes more gradually (e.g. deprecate
> things) and try to introduce features (if possible) in a way that they can
> be "switched off".
>
> Even on OS level there is a requirement note and sometimes API changes have
> > impact on applications and their complete compatibility.
> >
>
> IMHO users just expect things to work out of the box. More if they are just
> very satisfied with the version of the product they are using and the only
> reason they are actually migrating is just to not "fall behind". There was
> already something called Wicket 2.0 which was abandoned after a few months
> of development because, if I remember correctly, it broke too much previous
> version code base. As a user I would like not to experience something
> similar anymore. I haven't tried yet Wicket 8.x but I'm a bit afraid it
> might be a bit disruptive for some users/applications. I will want to try
> it ASAP and give my modest feedback.
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 make to
deliver new versions and improve the framework. So, what I tell bellow is
with full respect to that.
I'm NOT really "complaining" let's say I'm just voicing some concerns from
users. This is the second Wicket application I migrate to Wicket 7.0 in
last two of months. First application was for a customer and we encountered
a few little "surprises", e.g.
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.markup.html.panel.FeedbackPanelDonotsetCSSclassontheli
>spanelementforafeedbackmessageWICKET-4831
IMHO changes like this bring no real value and just make migrations less
"stable". Not to mention things like this
https://ci.apache.org/projects/wicket/guide/7.x/guide/componentQueueing.html
which might have made framework slower (according to certain post on
list). I know that without changes there is no evolution. I'm just telling
that maybe there is a need to make changes more gradually (e.g. deprecate
things) and try to introduce features (if possible) in a way that they can
be "switched off".
Even on OS level there is a requirement note and sometimes API changes have
> impact on applications and their complete compatibility.
>
IMHO users just expect things to work out of the box. More if they are just
very satisfied with the version of the product they are using and the only
reason they are actually migrating is just to not "fall behind". There was
already something called Wicket 2.0 which was abandoned after a few months
of development because, if I remember correctly, it broke too much previous
version code base. As a user I would like not to experience something
similar anymore. I haven't tried yet Wicket 8.x but I'm a bit afraid it
might be a bit disruptive for some users/applications. I will want to try
it ASAP and give my modest feedback.
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Posted by Tobias Soloschenko <to...@googlemail.com>.
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 <re...@gmail.com>:
>
> 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-D28fww9fXCk6xgyvCCx0A@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 <mg...@apache.org>
> 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 <
>> reiern70@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 <mg...@apache.org>
>>> wrote:
>>>
>>>> On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro <
>>>> reiern70@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 <
>>>>> reiern70@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 <
>>>>>> reiern70@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 <
>>>>>>> reiern70@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 <
>>>>>>>> reiern70@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 <sv...@meiers.net>
>>> 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 <
>>>>>>>>>>> reiern70@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 <
>>>>>>>>>>>> reiern70@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Sven,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for the feedback. It should not be the case
>>>>>>>>>>>>>
>>>>>>>>>>>>> radioGroup = new RadioGroup<T>("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 <sven@meiers.net
>>>
>>>>>>>>>>>>> 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-unsubscribe@wicket.apache.org
>>>>>>>>>>>>>> For additional commands, e-mail:
>> users-help@wicket.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards - Ernesto Reinaldo Barreiro
>>>
>>>
>>>
>>> --
>>> Regards - Ernesto Reinaldo Barreiro
>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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-D28fww9fXCk6xgyvCCx0A@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 <mg...@apache.org>
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 <
> reiern70@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 <mg...@apache.org>
> > wrote:
> >
> > > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro <
> > > reiern70@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 <
> > > > reiern70@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 <
> > > >> reiern70@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 <
> > > >>> reiern70@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 <
> > > >>>> reiern70@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 <sv...@meiers.net>
> > 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 <
> > > >>>>>>> reiern70@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 <
> > > >>>>>>>> reiern70@gmail.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>> Hi Sven,
> > > >>>>>>>>>
> > > >>>>>>>>> Thanks for the feedback. It should not be the case
> > > >>>>>>>>>
> > > >>>>>>>>> radioGroup = new RadioGroup<T>("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 <sven@meiers.net
> >
> > > >>>>>>>>> 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-unsubscribe@wicket.apache.org
> > > >>>>>>>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> --
> > > >>>>>>>>> Regards - Ernesto Reinaldo Barreiro
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Regards - Ernesto Reinaldo Barreiro
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > ---------------------------------------------------------------------
> > > >>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > >>>>>> For additional commands, e-mail: users-help@wicket.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> Regards - Ernesto Reinaldo Barreiro
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>> Regards - Ernesto Reinaldo Barreiro
> > > >>>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> 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?
Posted by Martin Grigorov <mg...@apache.org>.
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 <
reiern70@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 <mg...@apache.org>
> wrote:
>
> > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro <
> > reiern70@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 <
> > > reiern70@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 <
> > >> reiern70@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 <
> > >>> reiern70@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 <
> > >>>> reiern70@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 <sv...@meiers.net>
> 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 <
> > >>>>>>> reiern70@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 <
> > >>>>>>>> reiern70@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>> Hi Sven,
> > >>>>>>>>>
> > >>>>>>>>> Thanks for the feedback. It should not be the case
> > >>>>>>>>>
> > >>>>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net>
> > >>>>>>>>> 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-unsubscribe@wicket.apache.org
> > >>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> --
> > >>>>>>>>> Regards - Ernesto Reinaldo Barreiro
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Regards - Ernesto Reinaldo Barreiro
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > ---------------------------------------------------------------------
> > >>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >>>>>> For additional commands, e-mail: users-help@wicket.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Regards - Ernesto Reinaldo Barreiro
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> 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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <mg...@apache.org>
wrote:
> On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro <
> reiern70@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 <
> > reiern70@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 <
> >> reiern70@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 <
> >>> reiern70@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 <
> >>>> reiern70@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 <sv...@meiers.net> 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 <
> >>>>>>> reiern70@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 <
> >>>>>>>> reiern70@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Hi Sven,
> >>>>>>>>>
> >>>>>>>>> Thanks for the feedback. It should not be the case
> >>>>>>>>>
> >>>>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net>
> >>>>>>>>> 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-unsubscribe@wicket.apache.org
> >>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Regards - Ernesto Reinaldo Barreiro
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Regards - Ernesto Reinaldo Barreiro
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Regards - Ernesto Reinaldo Barreiro
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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?
Posted by Martin Grigorov <mg...@apache.org>.
On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro <
reiern70@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 <
> reiern70@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 <
>> reiern70@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 <
>>> reiern70@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 <
>>>> reiern70@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 <sv...@meiers.net> 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 <
>>>>>>> reiern70@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 <
>>>>>>>> reiern70@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi Sven,
>>>>>>>>>
>>>>>>>>> Thanks for the feedback. It should not be the case
>>>>>>>>>
>>>>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net>
>>>>>>>>> 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-unsubscribe@wicket.apache.org
>>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <
reiern70@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 <
> reiern70@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 <
>> reiern70@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 <
>>> reiern70@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 <sv...@meiers.net> 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 <
>>>>>> reiern70@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 <
>>>>>>> reiern70@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi Sven,
>>>>>>>>
>>>>>>>> Thanks for the feedback. It should not be the case
>>>>>>>>
>>>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net>
>>>>>>>> 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-unsubscribe@wicket.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <
reiern70@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 <
> reiern70@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 <
>> reiern70@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 <sv...@meiers.net> 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 <
>>>>> reiern70@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 <
>>>>>> reiern70@gmail.com> wrote:
>>>>>>
>>>>>> Hi Sven,
>>>>>>>
>>>>>>> Thanks for the feedback. It should not be the case
>>>>>>>
>>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
@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 <
reiern70@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 <
> reiern70@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 <sv...@meiers.net> 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 <
>>>> reiern70@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 <
>>>>> reiern70@gmail.com> wrote:
>>>>>
>>>>> Hi Sven,
>>>>>>
>>>>>> Thanks for the feedback. It should not be the case
>>>>>>
>>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <
reiern70@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 <sv...@meiers.net> 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 <
>>> reiern70@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 <
>>>> reiern70@gmail.com> wrote:
>>>>
>>>> Hi Sven,
>>>>>
>>>>> Thanks for the feedback. It should not be the case
>>>>>
>>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Regards - Ernesto Reinaldo Barreiro
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards - Ernesto Reinaldo Barreiro
>>>>
>>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <sv...@meiers.net> 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 <
>> reiern70@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 <
>>> reiern70@gmail.com> wrote:
>>>
>>> Hi Sven,
>>>>
>>>> Thanks for the feedback. It should not be the case
>>>>
>>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Regards - Ernesto Reinaldo Barreiro
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards - Ernesto Reinaldo Barreiro
>>>
>>>
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and
AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Posted by Sven Meier <sv...@meiers.net>.
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 <
> reiern70@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 <
>> reiern70@gmail.com> wrote:
>>
>>> Hi Sven,
>>>
>>> Thanks for the feedback. It should not be the case
>>>
>>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards - Ernesto Reinaldo Barreiro
>>>
>>
>>
>>
>> --
>> Regards - Ernesto Reinaldo Barreiro
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <
reiern70@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 <
> reiern70@gmail.com> wrote:
>
>> Hi Sven,
>>
>> Thanks for the feedback. It should not be the case
>>
>> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@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?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
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 <
reiern70@gmail.com> wrote:
> Hi Sven,
>
> Thanks for the feedback. It should not be the case
>
> radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior
on wickte 7?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi Sven,
Thanks for the feedback. It should not be the case
radioGroup = new RadioGroup<T>("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 <sv...@meiers.net> 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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: are there any changes to radioGroup and
AjaxFormChoiceComponentUpdatingBehavior on wickte 7?
Posted by Sven Meier <sv...@meiers.net>.
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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org