,
Michal Wegrzyn
> -Original Message-
> From: Michal Wegrzyn
> Sent: Thursday, February 02, 2012 15:05
> To: 'users@wicket.apache.org'
> Subject: RE: 1.5 Behaviors
>
> Are they any other behaviors attached?
>
> Best regards,
> Michal Wegrzyn
>
&g
..@gmail.com]
> > Sent: Thursday, February 02, 2012 14:00
> > To: users@wicket.apache.org
> > Subject: Re: 1.5 Behaviors
> >
> > Any clue on what it could be?
> >
> > 2012/2/2 nino martinez wael
> >
> > > it's never called on the behavio
Are they any other behaviors attached?
Best regards,
Michal Wegrzyn
> -Original Message-
> From: nino martinez wael [mailto:nino.martinez.w...@gmail.com]
> Sent: Thursday, February 02, 2012 14:00
> To: users@wicket.apache.org
> Subject: Re: 1.5 Behaviors
>
> Any clu
Any clue on what it could be?
2012/2/2 nino martinez wael
> it's never called on the behavior and neither are isEnabled... It must be
> something higher up the hierarchy that are stopping the behavior
> processing..
>
>
>
> 2012/2/2 Martin Grigorov
>
>> See org.apache.wicket.Component#canCallLi
it's never called on the behavior and neither are isEnabled... It must be
something higher up the hierarchy that are stopping the behavior
processing..
2012/2/2 Martin Grigorov
> See org.apache.wicket.Component#canCallListenerInterface
>
> On Thu, Feb 2, 2012 at 12:25 PM, nino martinez wael
>
See org.apache.wicket.Component#canCallListenerInterface
On Thu, Feb 2, 2012 at 12:25 PM, nino martinez wael
wrote:
> Hi
>
> What can cause a behavior not to be processed?
>
> I have a structure like this:
>
> Form
> --FieldSet
> ---inputs...
>
> I have an appender on the fieldset which is a webm
