Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.2
-
Fix Version/s: 3.0.RC2, 3.0, EE-2.0.0.GA_P01
-
Component/s: Bridge, Framework, ICE-Components
-
Labels:None
-
Environment:ICEfaces 2
-
Assignee Priority:P1
-
Affects:Compatibility/Configuration
-
Workaround Exists:Yes
-
Workaround Description:Where possible, use <f:ajax disabled="true"> with h:commandButton instead of h:commandLink.
Description
There are use cases where it's desirable to disable Ajax request processing for specific components. Since ICEfaces automatically enables Ajax for stock components and components that adhere to standard JSF APIs, the recommended strategy is to disable ajax using <f:ajax disabled="true">.
Testing of the current trunk shows that this technique is currently working for h:commandButtons but not for h:commandLinks.
Testing of the current trunk shows that this technique is currently working for h:commandButtons but not for h:commandLinks.
Issue Links
- blocks
-
ICE-7405 Setting <f:ajax disabled="true"> does not work for h:commandLink and h:commandButton having an f:param
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion