HttpSessionBindingListener, HttpSessionListener : Session already invalidated

knows how to get code called BEFORE the sesion dies? Cordialement, Nicolas Silberzahn Digital Airways Everywhere Technologies www.DigitalAirways.com o Google said be aware there is a ">" at the end that belongs to the URL... http://www.apachelabs.org/tomcat-de

RE: Rep. : [JSP/JAVABEANS] set method and empty parameters...

Bonjour, Does the browser send the information? Bonne journee, Nicolas Silberzahn Digital Airways Everywhere Technologies www.DigitalAirways.com >-Message d'origine- >De : Olivier Boulanger [mailto:[EMAIL PROTECTED]] >Envoye : mardi 12 mars 2002 12:49 >A : Tomcat

RE: IlligalStateException -- getOutputStream() has already been called for this response.

Bonjour, getOutputStream() can be done only once. I guess the first servlet you are invoking is doing it. Then you forward to a jsp which try to do it again If it forwards to a jsp, the initial servelt don't have to send something on the stream, thus don't have to call getOutputStream() . Bo

RE: IlligalStateException -- getOutputStream() has already been called for this response.

Bonjour, getOutputStream() can be done only once. I guess the first servlet you are invoking is doing it. Then you forward to a jsp which try to do it again If it forwards to a jsp, the initial servelt don't have to send something on the stream, thus don't have to call getOutputStream() . Bo

RE: Unable to compile class for JSP

I Get the same problem. The above import fixed the problem. This as not mandatory with TC3? It worked fine without the import... Nicolas Silberzahn Digital Airways Everywhere Technologies <100% Java, Mobile, Offline aware>Wapaka Browser www.DigitalAirways.com >-Message d'or

RE: IlligalStateException -- getOutputStream() has already been called for this response.

Bonjour, getOutputStream() can be done only once. I guess the first servlet you are invoking is doing it. Then you forward to a jsp which try to do it again If it forwards to a jsp, the initial servelt don't have to send something on the stream, thus don't have to call getOutputStream() . Bo

RE: problem in using

i can't believe my eiyes. Finding a class is a very 'basic' task for TomCat! I can't believe that any TomCat developper didn't make a test with a bean!!! We should have missed something... Nicolas Silbe*rzahn Digital Airways Everywhere Technologies <100% Java, Mobile, Offline aware>Wapaka Brows

RE: problem in using

Sorry, this is not an answer, just a word to say i face the same problem. With TomCat 3.3, all where ok. Installed 4 this morning, And when referencing a bean from a jsp, i get: org.apache.jasper.JasperException: Unable to compile class for JSP An error occured between lines: 72 and 83 in the