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.
I am still observing this behavior in iceface 1.8.0. Any update on if/when this will get fixed?