This content has been marked as final.
Show 2 replies
-
1. Re: @LoggedInInterceptor
quilleashm Dec 21, 2006 6:39 PM (in response to lle)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 session to the first one.
Step through your Interceptor after clicking the link and see where it goes wrong.
HTH.
Mike. -
2. Re: @LoggedInInterceptor
lle Dec 21, 2006 7:21 PM (in response to 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.