Hello Harald,
one interessting approach is when you're developing an application for
different presentation layers e.g. JSF and SWT. With the "typesave"
Viewconfig you are abled to build one single java based navigation
handling and use it in multiple presentation layers, apart from
faces-config.xml
Just for simple JSF applications I would use it just for security
reasons with @Secured Annotation.
Regards
Florian
Quoting Harald Wellmann <[email protected]>:
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
