Hi!
Imagine a component inside of your page:
<x:viewGroup="admin"/>
Stuff like this might work only with Facelets or JSF 1.2 as we need this
information before any binding has been issued. A binding might request
a bean in a conversation which might be started then and so we are no
longer able to have the @ConversationRequire tag.
We already though about something like <x:viewController="#{bean}" /> so
that you have no reference to the page from your backing bean .... But
the problems above prohibits this for now.
An extra config through a bean definition might work, though.
@ViewController(viewGroups={"admin", "edit"})
public class Editor
{
...
Thoughts?
Sound like a good idea.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Perhaps like @PreRenderView (executeOn={"/edit1.xhtml"})
Why would you combine all in one ViewController and then split the
method execution per page?
However, I am open for each enhancement which we find usable in the end.
What will be the semantic of:
@PreRenderView (executeOn={"/edit1.xhtml"})
@PreRenderView (executeOn={"/edit2.xhtml"})
@PreRenderView ()
Would you expect the 3rd PreRenderView to be invoked an each page or only on
those not configured explicitly?
Ciao,
Mario
