Rather than a JDBC appender I was hoping for a more generic appender that could use JPA or something else.
On Apr 25, 2013, at 7:39 AM, Nicholas Williams wrote: > First, a quick question: do we anticipate the next version to be beta6 or > rc1? Just curious. > > I'm currently working on cleaning up compiler warnings throughout the project > and should have that completed soon. > > I want to go ahead and get the conversation started about database appenders. > I'd like to see two appenders: > > - A JdbcAppender that is capable of logging to any RDBMS for which there is a > JDBC driver. > - A MongoAppender that is capable of logging to a MongoDB database. > > The JdbcAppender and MongoAppender would, as far as I can tell, need > properties for mapping all of the possible logging event properties to table > columns (or Mongo equivalent). I don't really see any other way to accomplish > that. We could use layout patterns from the PatternLayout to achieve this: > <column name="columnName" pattern="PatternLayout equivalent-pattern" /> > > I imagine the JdbcAppender having mutually exclusive properties for JDBC > URL/username/password, DataSource JNDI URL, and class.staticFactoryMethod for > obtaining a DataSource. > > The MongoAppender would similarly have mutually exclusive properties for > connection information and class.statucFactoryMethod for obtaining a Mongo > instance. > > I'd like to take a stab at these after I complete fixing compiler warnings, > and wanted to start getting feedback/ideas and also see if anyone has use > cases for other NoSQL appenders. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
