The other benefit I can see with this is to get "global" outcome support with
annotations is simply with constants.
public class A {
@NagivigationRule(outcome=JsfNavOutcome.FAILED,
view=JsfView.ERROR_PAGE)
public String a() {}
}
public class B {
@NagivigationRule(outcome=JsfNavOutcome.FAILED,
view=JsfView.ERROR_PAGE)
public String a() {}
}
This could lead to all things, possibly even using EL expressions as the view
ID and such. As a result, I think it would become much more flexible (although
possibly harder to maintain) than normal XML nav.
Or perhaps I am just over doing design eh?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940414#3940414
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940414
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
