Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0-Beta1
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:ICEfaces 2 + Mojarra 2
-
ICEsoft Forum Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
Users are migrating ICEfaces 1.8.x applications to ICEfaces 2, and finding that dynamic ui:includes are not working. We need to investigate why this is, and come up with either code changes, or a new technique that developers should use. This should be documented in the wiki, in its own page, and link to by: http://wiki.icefaces.org/display/ICE/Compatibility
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Adding the forum reference.
At this point, the test case is working for us. I'll build a .war and try it on Glassfish 3 with Mojarra 2.0.3 (as I ran on Tomcat previously). If it runs as expected, then I'll post the .war file to the forum for the poster to try in their environment.
Show
Deryk Sinotte
added a comment - Adding the forum reference.
At this point, the test case is working for us. I'll build a .war and try it on Glassfish 3 with Mojarra 2.0.3 (as I ran on Tomcat previously). If it runs as expected, then I'll post the .war file to the forum for the poster to try in their environment.
Our test case appears to work and I can't duplicate the issue described in the forum so marking this resolved (Can't Reproduce).
Show
Deryk Sinotte
added a comment - Our test case appears to work and I can't duplicate the issue described in the forum so marking this resolved (Can't Reproduce).
Based on a conversation that Mark and I had, I've heavily modified the test case (icefaces2/samples/test/dyninc) to provide 3-way page navigation as well as output a bit more information. The basic finding is the same as noted in the discussion in that both stock JSF and ICEfaces with compat components appear to behave in the same way. Adding the 3rd page did show the behaviour that Mark hypothesized with the navigation defaulting back to the default page when the navigation bean is request scoped. To summarize:
Request-scoped bean: The initial include correctly renders the default - page 1. Switching to dynamically include page 2 or 3 works but subsequent navigation always returns to page 1.
View-scoped bean: The initial include correctly renders the default - page 1. Switching to dynamically include page 2 or 3 works but subsequent navigation does not work - whatever page your are on you stay on.
Session-scoped bean: Dynamic includes appear to work all over.
Window-scoped bean: Dynamic includes appear to work if the page is enabled for ICEfaces. In stock JSF it behaves as a Request-scoped bean.