When I say protected, I mean that either:
a) login-required="true" is set in pages.xml
b) A element is specified in pages.xml
or
c) A component method is annotated with @Restrict
As for the silent authentication, look at Identity.hasRole() and Identity.checkPermission(), both of these methods call isLoggedIn(true), which will attempt to authenticate if the user's credentials are set.
I have tested this code and it all works as expected. If you are experiencing problems then perhaps there is something particular to your use case that I am missing. If you would like to raise an issue in JIRA with a reproducible test case then I'd be happy to look at it for you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125383#4125383
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125383
Thanks for the clarification, really appreciate it.
I don't have the required insight knowledge in order to provide a good solution. One suggestion I have would be: it seems that the components need to registered with seam first in order to be used. Theoretically, a map from the component's names to the component can be built for fast look up whenever a component is referenced. I do think this worth given the extra care as component references are everywhere in a Seam application.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125369#4125369
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125369