Makes sense to me. Any thoughts of taking things a bit further, though, like
assigning identifiers to views which aren't assigned to the view id name?
This would allow you to assign a ViewController to groups of pages easily.
Imagine a component inside of your page:
<x:viewGroup="admin"/>
This could also be done via a Spring bean definition. The annotation would
then be something like this:
@ViewController(viewGroups={"admin", "edit"})
public class Editor
{
...
Thoughts?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Matthias Wessendorf
> Sent: Sunday, October 21, 2007 11:13 AM
> To: MyFaces Development
> Subject: [Orchestra] ViewController
>
> Hi,
>
> I am using the build from today, and I use the ViewController (as a
> multi vc) like:
>
> @ViewController(viewIds={"/edit1.xhtml", "/edit2.xhtml"})
> public class Editor
> {
> ...
> @PreRenderView public void loader()
> {
> //do some work...
> }
> ...
> }
>
> I'd like to parametrize the call of the loader() only on a particular
> viewId,
> like on the first page (edit1.xhtml) and not always.
>
> Perhaps like @PreRenderView (executeOn={"/edit1.xhtml"})
>
> Any thoughts ?
>
> -M
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
