Re: TC4's classloader choking on xerces.jar (maybe)

2001-01-21 Thread Gokul Singh
- Original Message - From: "Craig R. McClanahan" <[EMAIL PROTECTED]> > Tomcat 4 follows the new rules in the servlet 2.3 PFD spec, which allows a > container to change this so that loading starts with your WEB-INF areas first. > > Consider the following scenario - I put a copy of the Pos

Re: NullPointerException from HttpSessionFacade.invalidate()

2001-01-14 Thread Gokul Singh
- Original Message - From: "Hans Bergsten" <[EMAIL PROTECTED]> > > Gokul Singh wrote: > > > > Hans Bergsten wrote: > > > [...] > > > > I am trying to disallow a single user to have multiple login sessions > > valid at

Re: NullPointerException from HttpSessionFacade.invalidate()

2001-01-14 Thread Gokul Singh
hris on this.   >  This probably needs to be summarized and sent as > spec feedback, but unless he says otherwise I will> assume Gokul Singh is going to do it (Gokul?)   I think the specs do need to clarify this matter. So I think I am going to summarize it and send it to spec feedback.   Regds, Gokul > > -cks>

Re: NullPointerException from HttpSessionFacade.invalidate()

2001-01-14 Thread Gokul Singh
Hans Bergsten wrote:> [...]> The spec may not be explicit enough about this, but the session object> you get back from the getSession() object is a container-managed object> that the application is not supposed/allowed to keep long-lived> references > to. It's the same as with all other cont

Re: NullPointerException from HttpSessionFacade.invalidate()

2001-01-12 Thread Gokul Singh
- Original Message - From: Craig R. McClanahan To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Thanks for looking into the problem. I think the I was not able to convey the problem properly. I have some clarifications below. > The session object is valid for more than one request, but only u

NullPointerException from HttpSessionFacade.invalidate()

2001-01-11 Thread Gokul Singh
Hi,I am trying to build a login servlet and get a NullPointerException from HttpSessionFacade class in Tomcat 3.2.1.The code of the simple version of the servlet which reproduces theproblem is attached at the end of this mail along with the stack trace of the Exception thrown.This piece of