Re-enabling a disable commandButton does not fire ajax call

UI Components for JSF
mang
Posts: 20
Joined: 05 Aug 2010, 02:10

28 Feb 2011, 09:48

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

9902468
Posts: 14
Joined: 14 Apr 2011, 07:45

19 Jul 2011, 07:57

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

cagatay.civici
Prime
Posts: 18616
Joined: 05 Jan 2009, 00:21
Location: Cybertron
Contact:

19 Jul 2011, 08:36

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/

9902468
Posts: 14
Joined: 14 Apr 2011, 07:45

19 Jul 2011, 12:32

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

Post Reply

Return to “PrimeFaces”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 22 guests