Hi, If you look at the archives for the tomcat-user, struts-user, log4j-user, and jboss mailing lists, you'll see many questions and problems that arise when the mixing is imperfect, i.e. some components use commons-logging and some don't, some classloaders see it and some don't, etc. It's a good concept and good implementation, and only getting better as server docs improve in this area, but it's given us (people who support above products) significant grief since its debut.
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Baum, Karl [mailto:[EMAIL PROTECTED] >Sent: Wednesday, July 14, 2004 3:03 PM >To: Jakarta Commons Developers List >Subject: RE: commons cache > >Hi. I am interested in what you are talking about. Obviously I am very >new to this list being that I joined a couple of hours ago. From my >point of view as a user, commons-logging seems to be a very successful >project. It has made it's way into countless other open source projects >because of the flexibility it brings with it. For example, a project >like cocoon shouldn't be forcing a logging implementation on anyone that >uses it. It also should not be forcing JCS on anyone when there are >other viable implementations of caching out there. > >-----Original Message----- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: Wednesday, July 14, 2004 2:51 PM >To: Jakarta Commons Developers List >Subject: RE: commons cache > > >Hi, > >>What I am getting at is I think I am interested in starting a project >>around the idea of a thin wrapper around other caching implementations. > ><rollingEyes> >I just years of commons-logging complaints running through my head... ></rollingEyes> > >That's my only thought at the moment. Note a vote against this, just an >association in my head... > >Yoav > > > >This e-mail, including any attachments, is a confidential business >communication, and may contain information that is confidential, >proprietary and/or privileged. This e-mail is intended only for the >individual(s) to whom it is addressed, and may not be saved, copied, >printed, disclosed or used by anyone else. If you are not the(an) >intended recipient, please immediately delete this e-mail from your >computer system and notify the sender. Thank you. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
