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-enabling a disable commandButton does not fire ajax call
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
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/
For spring users;
http://cagataycivici.wordpress.com/2010 ... pring-3-0/
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
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
-
- Information
-
Who is online
Users browsing this forum: No registered users and 43 guests