This content has been marked as final.
Show 5 replies
-
1. Re: actions defined in pages.xml
delphi'sghost Jun 27, 2007 5:16 PM (in response to youngm)I forget what the difference is between render and redirect, but I usually use redirect in pages.xml.
<page view-id="/list.xhtml"> <navigation if-outcome="detail"> <redirect view-id="/detail.xhtml"/> </navigation> </page> <page view-id="/detail.xhtml" action="#{bean.loadDetail}"/>
Give that a whirl... -
2. Re: actions defined in pages.xml
youngm Jun 27, 2007 5:33 PM (in response to youngm)Unfortunately I don't want to do a redirect here because I'm passing some other request parameters in and they get dropped after the redirect???
-
3. Re: actions defined in pages.xml
gavin.king Jun 27, 2007 6:30 PM (in response to youngm)"youngm" wrote:
I'm attempting to get the hang of pages.xml. If I do:<page view-id="/list.xhtml"> <navigation if-outcome="detail"> <render view-id="/detail.xhtml"/> </navigation> </page> <page view-id="/detail.xhtml" action="#{bean.loadDetail}"/>
When I navigate from /list.xhtml to /detail.xhtml the #{bean.loadDetail} expression is never called. However if I just hit /detail.xhtml directly the action is called. Is this a bug or expected behaviour of some sort?
Mike
Um, it should work, I think... -
4. Re: actions defined in pages.xml
youngm Jun 28, 2007 11:51 AM (in response to youngm)There was an error in my example it should actually be:
<page view-id="/list.xhtml"> <navigation> <rule if-outcome="detail"> <render view-id="/detail.xhtml"/> </rule> </navigation> </page> <page view-id="/detail.xhtml" action="#{bean.loadDetail}"/>
But that doesn't work either....I'll file a bug. -