monroe wrote:Given your situation, it might be easier just to put the user id in the application Session space and write your own SSO implementation.
FWIW, in the jForum web environment, the RequestContext interface is implemented by the WebRequestContext with is just a "wrapped" HttpServletRequest. So, you can cast this object to HttpServletRequest and get all the normal methods like getSession(), etc.
If you're wondering why it's this way, it is to abstract the application a little bit from the underlying application environment. This makes it easy to create the StandardRequestContext implementations which can be used in testing harnesses and other non-J2EE environments.
I not understand..., if user is load in session, Can't i use one Servlet of my webapp out of JForum to load it, and when JForum load, load user too?, what is the problem of this?.
You say me that i cast WebRequestContext and edit it to load my user..., but, if I havent loaded JForum before.
I must load JForum class, before that i cast my edit WebRequestContext?, because i believe that JForum must is load in this moment..., is correct?
[originally posted on jforum.net by MiLLeN]