Page 2 of 2
Re: Re-enabling a disable commandButton does not fire ajax c
Posted: 28 Feb 2011, 09:48
by mang
I tested the same example using h:commandButton and found that h:commandButton behave similarly to p:commandButton.
So I guess it is not a bug and I have implemented a workaround solution to my problem with request scope.
Thanks
Mang
Mojarra-2.0.3
Glassfish v3
primefaces-2.2
Re: Re-enabling a disable commandButton does not fire ajax c
Posted: 19 Jul 2011, 07:57
by 9902468
Just ran into this issue also. This makes it impossible to use disabled / enabled buttons with request scoped backing beans.
How did you solve it? Did you extend the PF component?
- Ville
Re: Re-enabling a disable commandButton does not fire ajax c
Posted: 19 Jul 2011, 08:36
by cagatay.civici
Buttons do not process events when they are disabled, so if disabled option is a conditional EL it must be stateful, that's why I suggested viewscope.
For spring users;
http://cagataycivici.wordpress.com/2010 ... pring-3-0/
Re: Re-enabling a disable commandButton does not fire ajax c
Posted: 19 Jul 2011, 12:32
by 9902468
Ok,
we were trying to enable / disable buttons via js in client side, but that fails if the button has different disabled status than when it was rendered out for the reason stated. We might have to settle for view scoped beans, but those have been so problematic with CDI integration that we use.
- Ville