|
Regards, I have a specific need with JSF to change some pages based
on runtime conditions. For example, some users of the app would see a form
rendered on a two-column table meanwhile others may get it rendered totally different,
even with different field order, according to a personalized template used by them.
I was thinking of using three scenarios for certain pages, and they would get
included according to runtime conditions of the current user, something like
this: <!—Static
Page Inclusion with standard page--> <ui:fragment rendered="#{searchTreeBean.scenario
== 0}> <ui:include src="/pages/standard.xhtml"
/> </ui:fragment> <!—Static
Page Inclusion with personalized page--> <ui:fragment rendered="#{searchTreeBean.scenario
== 1}> <ui:include src="/pages/personalized.xhtml"
/> </ui:fragment> <!—Dynamic
Page Inclusion with page inclusion at runtime according to value of:
"#{mybean.includedPage}" --> <ui:fragment rendered="#{searchTreeBean.scenario
== 2}> <ui:include src="#{mybean.includedPage}"
/> </ui:fragment> But I am not very sure if this is an adequate
strategy to support personalized pages for particular users, anyone has had a
similar problem? How have you proceeded? This has also lead me to think if
navigation conditions can be incorporated to the faces-config.xml file at
runtime? Cheers, Jorge Vásquez p.d: By the way, I am using Facelets as view
technology. |
