Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.5
-
Fix Version/s: 2.0-Beta2
-
Component/s: ICE-Components
-
Labels:None
-
Environment:all
Description
ICEfaces components often require the use of ICEfaces-specific classes to be used. This is not the desired style of development for EJB or other developers working with POJOs. The majority of ICEfaces component functionality should be accessible with primitive types, for instance, action methods should be available to cover actionListener functionality.
Activity
Ted Goddard
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Estimated Complexity | Medium | |
Fix Version/s | 2.0 [ 10032 ] | |
Affects Version/s | 1.5 [ 10027 ] | |
Affects Version/s | 1.6DR#2 [ 10040 ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.0-Beta [ 10231 ] | |
Fix Version/s | 2.0-Alpha3 [ 10032 ] |
Ken Fyten
made changes -
Fix Version/s | 2.0-Beta2 [ 10242 ] | |
Fix Version/s | 2.0-Beta1 [ 10231 ] |
Ken Fyten
made changes -
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
This consideration is part of the overall design requirement for the new Sparkle-platform based ICEfaces components.
Marking Fixed.