Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Log File by java package and jsp package not working
Date: Tue, 14 Dec 2004 16:15:31 -0600
Message-ID: 
 <616816C3DDC4D74EB11AC96F6D469C1438FDE4@MSPM1BMSGM16.ent.core.medtronic.com>
Thread-Topic: Log File by java package and jsp package not working
Thread-Index: AcTiKZv0JSKRt1TVRP6kvUCu7YYHPQAADNYw
From: "Hanson, Bryan" <bryan.hanson@medtronic.com>
To: "Log4J Users List" <log4j-user@logging.apache.org>

yes, but we are stuck with the folder structure we have, cannot change =
it.

Though we will be using BEA for awhile, no plans on changing it...so if =
we can stick with a particular webserver, could we then (somehow) make =
the logger able to determine servlet to log for?


-----Original Message-----
From: Jacob Kjome [mailto:hoju@visi.com]
Sent: Tuesday, December 14, 2004 4:02 PM
To: Log4J Users List
Subject: RE: Log File by java package and jsp package not working


Your loggers need not be named for their class.  In fact, for JSP's you =
can't
count on any particular naming scheme for the generated class.  I'm =
pretty sure
that is entirely implementation specific, so the class name generated =
for
"hello.jsp" maybe jsp_servlet_hello.java on Tomcat and =
hello_jsp_servlet.java
on Weblogic (I made these names up, but you get the point).  If you =
start
counting on one naming scheme, you will quickly find yourself tied to a =
server
implementation.

I suggest coming up with a standard naming scheme for your JSP's.  For =
instance,
have them all be within some common base fake package and, maybe have =
folder
names further distinguish the package.  Then, have the final name of the =
logger
itself be the name of the file (less ".jsp").  For instance, with the =
base
package "com.mycompany.jsp" and the following files...

hello.jsp
admin/manage.jsp
admin/another.jsp
help/howto.jsp

The loggers might be, respectively, named...

com.mycompany.jsp.Hello
com.mycompany.jsp.admin.Manage
com.mycompany.jsp.admin.Another
com.mycompany.jsp.help.HowTo

You'd do this by passing in these names rather than =
this.getClass().getName() to
the getLogger() method such as....

Logger logger =3D Logger.getLogger("com.mycompany.jsp.admin.Manage");

Your config, in order to display logger output for the "admin" package =
only,
would be...

  <logger name=3D"com.mycompany.jsp.admin" additivity=3D"false">
   <level value=3D"info"/>
   <appender-ref ref=3D"JSPAdmin"/>
  </logger>


Make sense?

Jake


Quoting "Hanson, Bryan" <bryan.hanson@medtronic.com>:
>
>
> I'm using log4J in a JSP with taglibs-log.  I'm trying to configure =
the
> log4j.xml such that it will put the JSP log message in a particular =
log file
> based on the JSP/servlet package.  So far, I have not been successful.
>
> Does anyone have ideas how to configure a log4j.xml to log JSP =
messages to
> package based log files?
>
>  <logger name=3D"jsp_servlet._capa" additivity=3D"false">
>   <priority value=3D"info"/>
>   <appender-ref ref=3D"JSPcapa"/>
>  </logger>
>
>
> We have "capa" directory with JSP pages in it.  The webserver compiles =
the
> jsp to jsp_servlet\_capa with the class package: package =
jsp_servlet._capa
>
>
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org