jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@octo.com>
Subject RE: Log properites setup in Cactus 1.4
Date Wed, 07 Aug 2002 07:25:37 GMT
Hi Shane,

> -----Original Message-----
> From: Shane Duan [mailto:sduan@borland.com]
> Sent: 06 August 2002 08:40
> To: Cactus Users List
> Subject: Log properites setup in Cactus 1.4
> Is it possible to make the client and server use the same
> log4j.properties file but still keep different output file name?

Almost, but not quite ... You could define different appenders for
different categories. However, some classes are used both on the client
and server side so there is no way to differentiate them. So, the strict
answer is no. Now you can use the same file (BTW, this is mentioned in
the Web site documentation, under the Configuration Howto page). It will
simply contain information for both with the limitation of the file
being recreated for each client side TestCase (see doc).

> In JBuilder, all resource files are copied automatically to the output
> directory.  It is not that easy to specify that certain file needs to
> included in client classpath and certain file needs to be in the web
> archive file (web archive file is built from the output directory).  I
> could create an Ant script and configure JBuilder to run it every time
> it does the compile, but it is just such a hassle not to mention I
> to explain to others.
> If instead of property "log4j.appender.cactus.File", two properties,
> maybe "log4j.appender.cactus.server.File" and
> "log4j.appender.cactus.client.File" are used to specify the server and
> client log file, it is be a lot better.

Er... Are you suggesting you want to modify Log4j ;-) ?


> Thanks.
> Shane
> --
> Disclaimer:  I join all the news groups out of my own interest.  All
> opinions expressed here are my own and not necessarily those of my
> employer.
> Borland -- Enabling the digital world where our customers have the
> of choice to develop, deploy, and integrate applications across the
> enterprise and  the Internet. http://www.borland.com
> This e-mail, and any attachments thereto, is intended only for use by
> addressee(s) named herein and may contain legally privileged and/or
> confidential information.  If you are not the intended recipient of
> e-mail, you are hereby notified that any dissemination, distribution
> copying of this e-mail, and any attachments thereto, is strictly
> prohibited.  If you have received this e-mail in error, please
> and permanently delete the original and any copy of any e-mail and any
> printout thereof.
> --
> To unsubscribe, e-mail:   <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:cactus-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:cactus-user-help@jakarta.apache.org>

View raw message