Article:		A Look at Commons Chain, Part 1
Subject:		commons mire
Date:		2005-03-02 19:22:27
From:		craigpfeifer
Sounds neat, but how many other commons packages do you have to bring along as dependancies? Commons logging (among others) has some nasty runtime behavior that folks are quickly getting tired of.

Showing messages 1 through 2 of 2.

• commons mire
  2005-03-03 11:32:50  Bill Siggelkow | [View]
  
  
  I understand your point with Commons Logging -- it seems that
  this is an issue that needs to be addressed (and may be, I have
  not researched the activity in this area). As far as Digester and
  BeanUtils, these subprojects have proven to be quite valuable.
  Digester provides a lot of more to XML parsing that Chain uses
  -- why reinvent the wheel. Likewise with BeanUtils.
  
  I think you will also find that most open source frameworks leverage other frameworks. Just download Hibernate and look at how many additional JARs it ships with. The issue here is that Chain does not *ship* with these Jars -- perhaps this is just a build issue that could be addressed by the Commons team.
  

• commons mire
  2005-03-03 07:26:51  Taylor Cowan | [View]
  
  
  that's a good point I've not heard many make but needs to be dealt with. Each commons jar should be independent. Instead of using commons-logging or log4j, for example, it would use a logger interface, and have the dependency injected in any number of ways.
  <br/><br/>
  This concept has been in usage in the JDK with things like JDBC drivers, JAXP parsers and transformers, and while having to
  -DfooConcrete=my.foo.Implementation is sometimes inconvenient, it's certainly better than having to include 5 to 10 commons jars when you really only want one of them.