Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Fix Version/s: 3.0
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces 2.0, MyFaces 2.0
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration
Description
ICEfaces 2.0 should support MyFaces 2.0.
Issue Links
- blocks
-
ICE-6864
MyFaces' state writing triggers NPE in DOMResponseWriter
-
- Closed
-
-
ICE-7190
Enable support for portlets with MyFaces 2
-
- Closed
-
- depends on
-
ICE-7523
MyFaces 2: listeners registered with ace:ajax tags are not called
-
- Closed
-
-
ICE-5961
MyFaces 2.0 row selection corrupts table
-
- Closed
-
-
ICE-5962
MyFaces 2.0 effects corrupt panels
-
- Closed
-
-
ICE-5963
MyFaces 2.0 tree NotSerializableException
-
- Closed
-
-
ICE-5964
Myfaces 2.0 FacesMessages NotSerializableException
-
- Closed
-
-
ICE-5965
MyFaces 2.0 collapsiblePanel NullPointerException
-
- Closed
-
-
ICE-5966
Myfaces 2.0 Charts NotSerializableException
-
- Closed
-
-
ICE-5967
MyFaces 2.0 progressBar is not displayed
-
- Closed
-
-
ICE-5968
MyFaces 2.0 downloadResources NullPointerException
-
- Closed
-
-
ICE-5969
Transient fields break with MyFaces 2
-
- Closed
-
-
ICE-6116
MyFaces 2.0 incompatible with ice:config
-
- Closed
-
-
ICE-6622
Message(s) rendering for MyFaces
-
- Closed
-
-
ICE-7017
DeltaSubmit not working when configured to run against MyFaces
-
- Closed
-
-
ICE-7020
Pull down menus of popup calendar don't work with MyFaces
-
- Closed
-
-
ICE-7097
MyFaces state saving has different timing which impacts some components
-
- Closed
-
-
ICE-7099
MyFaces causes the GMap component to trigger a recursive full submit when choosing a location from the select menu.
-
- Closed
-
-
ICE-7105
Myfaces 2 "cannot find enclosing form" on alternate requests
-
- Closed
-
-
ICE-7118
MyFaces 2 and Push conflict - interferes with interaction in the Auction examples when run with MyFaces
-
- Closed
-
-
ICE-7182
The ICEfaces form decorations are not added during postbacks when running under MyFaces 2.
-
- Closed
-
-
ICE-7234
MyFaces 2 Regression Test Failure: year and month popups in the Calendar not working
-
- Closed
-
-
ICE-7235
MyFaces 2 Regression Test Failure: data paginator does not work properly
-
- Closed
-
-
ICE-7236
MyFaces 2 Regression Test Failure: dynamic changes to Locale are not reflected in the loadBundle messages
-
- Closed
-
-
ICE-7237
MyFaces 2 Regression Test Failure: navigation does not work properly
-
- Closed
-
-
ICE-7244
MyFaces 2: component ids with datatables include row index twice
-
- Closed
-
-
ICE-7417
MyFaces 2: ACE comp-suite example fails to find bridge.js and icepush.js resources if unique URLs are used
-
- Closed
-
-
ICE-6118
Enhance build scripts to allow for compiling and building libraries and samples against MyFaces
-
- Closed
-
-
ICE-7091
MyFaces 2 causes full forms to be updated after first Ajax request
-
- Closed
-
- is duplicated by
-
ICE-5858
Add support for MyFaces 2 in ICEfaces 2
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Linking in ace:ajax listener issue.
In running the scopes test, the view-scoped beans were not behaving properly with MyFaces. Turns out that the problem is due to a subtle interaction between inheritance and serialization.
The test contains a view-scoped bean declared as:
public class ViewScopedCounter extends Counter implements Serializable
the Counter superclass did not originally implement Serializable
public class Counter
It turns out that:
"When the super class is not serialized, when deserializing the instance of the sub class, the constructor of the super is called."
Because of this, the counter would always be set back to it's original value. By implementing Serializable on the superclass, the view-scoped beans work the same as they do in Mojarra.
public class Counter implements Serializable
Added ICE-7099 to address the problem with GMap where selecting a city from the drop down menu causes a recursive form submission when running with MyFaces.
Also explored the problem with the Rich Input Text component. Turns out that the problem only occurs if you clear the cookies and try and reload the page. Opened ICE-7100 to capture it. The problem is not confined to MyFaces so is not linked to this case.
Opened ICE-7097 to cover the issues with Chart and Progress Bar components which are related to the timing and strategy used for state saving.
FacesContext.getCurrentInstance() is null during application startup and this interferes with the initialization of a number of classes. This bug is present in MyFaces 2.0.0 but is verified fixed in the nightly builds, with target 2.0.1
The integration of MyFaces with the core framework and our sample applications is pretty much complete. From here on, individual issues that are MyFaces specific can be captured in their own distinct JIRAs.