[jboss-user] [JBoss Seam] - Re: LoggedInInterceptor

2007-01-18 Thread petemuir
The CVS reference manual has incomplete documentation View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003380#4003380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003380 ___ j

[jboss-user] [JBoss Seam] - Re: LoggedInInterceptor

2007-01-18 Thread lightbulb432
Where can I read up on the Seam Security Framework in the meantime? (Or where will I be able to read it next week?) I hope this Seam Security Framework will be a well-documented part of Seam... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003365#4003365 Re

[jboss-user] [JBoss Seam] - Re: LoggedInInterceptor

2007-01-18 Thread petemuir
The LoggedInInterceptor only prevents access to the bean (bijection, methods) not to the pages. I would advise you to wait for the Seam Security Framework due out next week for a comprehensive solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003214#4

[jboss-user] [JBoss Seam] - Re: @LoggedInInterceptor

2006-12-21 Thread lle
Thanks for your response. I figured it out. It actually has nothing to do with my LoggedInInterceptor. It's due to the security constraint I set in web.xml for accessing .xhtml files directly and I put ".xhtml" in my javascript when opening a new window. Sorry, false alarm :-) Thanks. View

[jboss-user] [JBoss Seam] - Re: @LoggedInInterceptor

2006-12-21 Thread quilleashm
Probably need to post your code but my best guess is the logged in information/marker is not available to the second window. If you are using a conversation scope this is likely. Using the session scope this may be possible as well depending on if a new window creates a different server side