Hi Daniel,
Yes, at Weblogic, request.getSession() is returning a non-null value AND
"(Settings) session.getAttribute(ATTR_NAME)" is
> working.
On Tomcat out of 5 requests this is happening for 2 times.
Let me explain the deployment architecture:
1. User invokes JSP page
2. JSP calls homegrown framework which performs operation and generates XML
response
2.1 This XML framework also works on sessions and request objects.
3. XSLT transforms XML into HTML and displays on UI
It looks like JSP and Servlets are using different sessions ???
Any pointers would be useful.
Regards,
Achal.
On Fri, Jul 3, 2009 at 9:05 PM, Daniel Henrique Alves Lima <
email_danie...@yahoo.com.br> wrote:
> Hi, Achal.
>
>
> On Fri, 2009-07-03 at 19:48 +0530, Achal Patel wrote:
> > Its basically below:
> >
> > HttpSession session = request.getSession();
> > Settings settings = (Settings) session.getAttribute(ATTR_NAME);
> >
> > I debugged it and got to know that session is getting null and again
> > invoking the same resource from UI serves fine.
> > The same is working fine on Weblogic.
>
> Am i missing something or you're saying that when session is null
> "(Settings) session.getAttribute(ATTR_NAME)" works ?
> Are you sure ?
>
> Or you're saying that, at Weblogic, request.getSession() is returning a
> non-null value AND "(Settings) session.getAttribute(ATTR_NAME)" is
> working ?
>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
--
Regards,
Achal Patel.
