Re: Exception starting filter Security Filter

Hi! In fact I was wrong in my last post. As I found out later, it did not work. I found a solution for my problem but I am not sure if it also applies to yours, Dan. Sorry for not sharing my knowledge until now, but it did not seem to interest anyone ;) During debugging I used a hacked

Re: Exception starting filter Security Filter

Cox, Charlie wrote: -Original Message- From: Volker Leidl [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 10, 2002 4:14 AM To: Tomcat Users List Subject: Re: Exception starting filter Security Filter Hi! In fact I was wrong in my last post. As I found out later, it did not work

Re: Repost: getClassLoader() returns null

classloader doc... Charlie -Original Message- From: Volker Leidl [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 12:24 PM To: Tomcat Users List Subject: Repost: getClassLoader() returns null Sorry for the repost, I don't mean to bother you, but can anyone confirm

Re: Repost: getClassLoader() returns null

? It would find your jar there before looking in /common/lib; in which case it would be loaded by the jvm's bootstrap and could return null. see the tomcat classloader doc... Charlie -Original Message- From: Volker Leidl [mailto:[EMAIL PROTECTED

Repost: getClassLoader() returns null

Sorry for the repost, I don't mean to bother you, but can anyone confirm that getClassLoader() on a class loaded by the common class loader of tomcat (4.0.3), particularily from a jar in common/lib, returns null? I'm really puzzled... Thanks in advance, Volker. ---BeginMessage--- Hi! I

getClassLoader() returns null

Hi! I just encountered a problem when using the commons-logging package together with Tomcat 4.0.3. When putting commons-loggin.jar (1.0.2) into the $TOMCAT_HOME/common/lib, in order to be available for the server classes as well as for all web apps, a NullPointerException is thrown when

RE: SERVLET CACHING PROBLEM IN TOMCAT- SNODX

Add reloadable=true to your webb apps context tag in server.xml. Volker. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 9:01 AM To: [EMAIL PROTECTED] Subject: SERVLET CACHING PROBLEM IN TOMCAT- SNODX Greetings,

RE: SERVLET CACHING PROBLEM IN TOMCAT- SNODX

It is reloadable (all lowercase). At least it works in my environment. If it still doesn't work, make sure that the system class loader has no access to your servlet (i.e. no CLASSPATH variable entry to the classes dir, etc.) so that the appropriate tomcat class loader handles these files.

Wrong line number in stack trace

Hi all! I repeatedly run into the problem that the stack trace of an exception thrown within a jsp page does not show the appropriate line number. For instance the output of the stack trace says: java.lang.Exception at

RE: Wrong line number in stack trace

? (It should be the source you looked at) -Ursprüngliche Nachricht- Von: Volker Leidl [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 29. November 2001 10:45 An: Tomcat Users List Betreff: Wrong line number in stack trace Hi all! I repeatedly run into the problem

RE: Wrong line number in stack trace

: Volker Leidl [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 29. November 2001 10:45 An: Tomcat Users List Betreff: Wrong line number in stack trace Hi all! I repeatedly run into the problem that the stack trace of an exception thrown within a jsp page does not show

RE: Wrong line number in stack trace

Volker Leidl, I worked on the problem that you posted. I feel that I have found out the cause of the problem that you are facing. I worked on a sample jsp file to get to the root of the problem. What is happening

RE: Wrong line number in stack trace

? -Ursprüngliche Nachricht- Von: Volker Leidl [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 29. November 2001 13:52 An: Tomcat Users List; [EMAIL PROTECTED] Betreff: RE: Wrong line number in stack trace Thanks a lot! This is exactly the problem. I also used EditPlus to view the code