On Fri, 13 Dec 2002, Manavendra Gupta wrote:
> Date: Fri, 13 Dec 2002 08:01:09 +0530 > From: Manavendra Gupta <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]>, > Manavendra Gupta <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: "null"s in tomcat logs > > Hi, > > I had posted a similar message (on the datasource thread) a few days ago, but I >guess it was lost in the flurry of "I don't understand the objective of this list" >messages. > > Below is a snippet of the tomcat 4.1 logs on my NT workstation. Notice there are two >"null" entries... while, both the filter as well as the DataSource work. My tomcat >4.1 setup on RHL 7.3 box shows me the nulls too, but the DataSource doesn't work >there (no, I'm not trying to mix two topics together). > > Anybody got any idea why there is this null entry in the log messages? I wouldn't worry about these. Consider what happens when the code that parses your XML file encounters a <filter> element. First, it creates an object of the corresponding class (FilterDef), then it configures the properties of that object based on the nested <filter-name> (and so on) elements. The debugging log prints out the toString() of the object at that time, and is simply showing you that the default values for some of the String properties on these configuration objects are null. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
