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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I am still observing this behavior in iceface 1.8.0. Any update on if/when this will get fixed?
Show
Brian Leathem
added a comment - I am still observing this behavior in iceface 1.8.0. Any update on if/when this will get fixed?
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