Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1-Beta
-
Fix Version/s: None
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ACE
Description
With our baseMeta inheritance mechanism, the properties that the JSF base classes provide all use their own getters/setters, which do not function well in dataTables, nor when combining programmatic calls to setters with ValueExpressions to those properties. We should investigate / audit those properties to see which ones we want to flip to using our generated properties and getter/setter methods, which fix all those problems. The issue would be the properties that are special in their implementation, such as id, value, etc. where they have behavioural side-effects that should not be overridden with our code.
An example of one we'd like to do is UIData.first, which the dataPaginator calls the setter for, but that an application might have a ValueExpression to, for controlling when the application change the page itself.
An example of one we'd like to do is UIData.first, which the dataPaginator calls the setter for, but that an application might have a ValueExpression to, for controlling when the application change the page itself.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This should be considered during a major release due to backwards compatibility concerns.