Details
-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 1.6
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Windows XP Professional
JBOSS 4.0.5.GA
-
ICEsoft Forum Reference:
-
Workaround Exists:Yes
-
Workaround Description:
Description
The following is a working navigation rule from the security demo:
<navigation-rule>
<from-view-id>/login.iface</from-view-id>
<navigation-case>
<from-action>#{authenticationController.authenticate}</from-action>
<from-outcome>success</from-outcome>
<to-view-id>/secure/main.iface</to-view-id>
<redirect/>
</navigation-case>
</navigation-rule>
When I added Facelets to the security demo, the navigation no longer worked. I found I had to remove the following entries for it to work:
<from-view-id>/login.iface</from-view-id>
and
<from-action>#{authenticationController.authenticate}</from-action>
I was able to confirm this in another demo using Facelets. It appears that <from-view-id> and <from-action> do not work when pairing ICEfaces with Facelets.
<navigation-rule>
<from-view-id>/login.iface</from-view-id>
<navigation-case>
<from-action>#{authenticationController.authenticate}</from-action>
<from-outcome>success</from-outcome>
<to-view-id>/secure/main.iface</to-view-id>
<redirect/>
</navigation-case>
</navigation-rule>
When I added Facelets to the security demo, the navigation no longer worked. I found I had to remove the following entries for it to work:
<from-view-id>/login.iface</from-view-id>
and
<from-action>#{authenticationController.authenticate}</from-action>
I was able to confirm this in another demo using Facelets. It appears that <from-view-id> and <from-action> do not work when pairing ICEfaces with Facelets.
Activity
Brad Kroeger
created issue -
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #15036 | Thu Oct 25 17:29:39 MDT 2007 | brad.kroeger | emailEditViewPanel.jspx - had to remove header facet tags, created webmailSplashPanel.jspx - had to remove f:verbatim tags, created ICE-2262 for this issue. faces-config.xml - removed <from-view-id> entry as per ICE-1957. webmail.jspx - All of the jsp:directive.include references have been replaced with ui:include. |
Files Changed | ||||
MODIFY
/projects/webmail/trunk/webmail/web/webmail.jspx
MODIFY /projects/webmail/trunk/webmail/web/WEB-INF/faces-config.xml MODIFY /projects/webmail/trunk/webmail/web/WEB-INF/web.xml MODIFY /projects/webmail/trunk/webmail/web/inc/contentPanels/emailEditViewPanel.jspx MODIFY /projects/webmail/trunk/webmail/build.xml MODIFY /projects/webmail/trunk/webmail/web/inc/contentPanels/webmailSplashPanel.jspx MODIFY /projects/webmail/trunk/webmail/web/login.jspx |
Brad Kroeger
made changes -
Field | Original Value | New Value |
---|---|---|
Workaround Description | Just use <from-outcome> in your navigation rule. |
The navigation rule only works if if the from-view-id is the resolved physical resource and the to-view-id is the resource with the virtual .iface extension. or Just use <from-outcome> in your navigation rule. |
Tyler Johnson
made changes -
Salesforce Case | [5007000000I0kWm] |
An email from Deryk:
I've been working on a test case that involves navigation so I've been trying both in-place (no <redirect/>) and redirected navigation. It seems that the only way I could get to work (either with or without the <redirect/> tag was to use something like the following:
<navigation-rule>
<from-view-id>/page01.jspx</from-view-id>
<navigation-case>
<from-outcome>next</from-outcome>
<to-view-id>/page02.iface</to-view-id>
<!-
<redirect/>-></navigation-case>
</navigation-rule>
This means that the navigation rule only works if if the from-view-id is the resolved physical resource and the to-view-id is the resource with the virtual .iface extension.
I haven't dug into the spec to see if the virtual extension thing is according to the rules or not. The user in this forum post seems to believe that it contravenes the specification.
http://www.icefaces.org/JForum/posts/list/7198.page