Re: log4j in Websphere EAR and classpath problem

I have no specific experience with Websphere, but it's pretty clear that it is using parent-first classloading behavior. I'm also guessing that you are using manual configuration of Log4j, at least for the webapps (a startup servlet or a servlet context listener, perhaps?). In this case, the l

Re: JDBCAppender and DB passwords

There's a couple ways. Both involve referencing variables set externally. For instance... ${db.username} ${db.password) You can make these variables available in one of two ways (only the first way below if you are using XML config) 1. Set it as a system property. e.g... java -Ddb.

log4j in Websphere EAR and classpath problem

I have a Websphere J2EE Struts application (packaged as an EAR), which contains one Java project (represented by a JAR file) with its own log4j configuration file with loggers and appenders, and two WEB Struts projects, each with its own configuration file, loggers and appenders. Both WEB projects

JDBCAppender and DB passwords

Hi list, I'm using log4j-1.2.14 and want to play with JDBCAppender. My main concern is the fact that in my log4j.properties file I need to provide the username and password details for the database connection. How can I use JDBCAppender without having to put this information in my .properties fil