a simple example is also @View(navigation = REDIRECT). you just need in one place if you inherit it. you will appreciate some advantages >esp.< in large applications or during the maintenance phase.
regards, gerhard 2013/3/28 Mark Struberg <[email protected]> > Harald, > > it gets more obvious if you add @Secured and page beans to the mix. > > You can centrally define the security rules for your pages (and folders) > and apply other cross cutting concerns very easily. > > LieGrue, > strub > > > > > ----- Original Message ----- > > From: Harald Wellmann <[email protected]> > > To: [email protected] > > Cc: > > Sent: Thursday, March 28, 2013 9:45 AM > > Subject: Re: Goals for JSF examples? > > > > Yes, I've seen these slides before. But I don't see what problem > > you're trying to solve. There are lots of annotations with unclear > > purpose. To me, this looks like a simple thing (i.e. navigation by > > view name, without faces-config.xml navigation rules) made complex for > > no obvious benefit. > > > > What does it help to have a class Pages.Index corresponding to > > /pages/index.xhtml? If I rename index.xhtml to welcome.xhtml, I > > probably have to rename Pages.Index to Pages.Welcome, there is no IDE > > refactoring doing that for me. So what's the point....? > > > > Best regards, > > Harald > > > > > > 2013/3/27 Gerhard Petracek <[email protected]>: > >> hi harald, > >> > >> for now you could have a look e.g. at [1] (esp. slide #4). > >> > >> regards, > >> gerhard > >> > >> [1] > >> > > > http://os890.blogspot.co.at/2012/02/slides-make-jsf-more-type-safe-with-cdi.html > >> > > >
