On Tue, 26 Feb 2002, James Strachan wrote: > I've just committed a minor patch to the SimpleLog class that catches any > security exceptions thrown inside the class constructor (when accessing > system properties) which occur when using the commons-logging component > inside a container.
Good catch ! I completely forgot the 'sandbox' case during the release. There is one more problem I found with the class loaders, we need to try Class.forName() if the thread loader fails. I doubt there are many other who'll notice this, but it's a valid use case and trivial fix. It happens if commons-logging is loaded in a child class loader, and the thread class loader is set to a different loader ( that will happen if the container is using commons-logging, and it uses a separate loader than the application ) Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
