Good to hear 1.1.1 solves the issue. And by the way, if you really do not want logging ever, then you could simply write your own trivial classes that implements classes org.apache.commons.logging.LogFactory and org.apache.commons.logging.Log and do nothing. That will save a little network traffic.
The SLF4J project provides a jar that does almost exactly that. Maybe at some time commons-logging should also provide a stub jar for that purpose. Regards, Simon ---- Steffen Breiler <[EMAIL PROTECTED]> schrieb: > Hello again, > > it is working now, unfortanely i forgot to compile it with > the new 1.1.1, but included the right on in the JAR archive. *doh* > > Thanks for your replies! > > -----Ursprüngliche Nachricht----- > Von: Rahul Akolkar [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 12. Dezember 2007 16:42 > An: [email protected] > Betreff: Re: Problem with logging in an applet > > On 12/12/07, Steffen Breiler <[EMAIL PROTECTED]> wrote: > > [Reposting from [EMAIL PROTECTED] > > > > Hey there, > > > > I've come across a problem, which i wasn't able to resolve myself. > > I wrote an applet using the httpclient, its in a JAR archive which is > > signed. > > The applet starts up and if it comes to the point of creating a > > httpclient > > instance: > > > > "HttpClient MyHTTPClient = new HttpClient();" > > > > ..it throws an exception: > > > > "Caused by: java.security.AccessControlException: access denied > > (java.util.PropertyPermission > > org.apache.commons.logging.LogFactory.HashtableImpl read)" > > > > I've read about this error somewhere, and that someone did a fix, > > which i was unable to download. > > > > I'm using the "commons-logging-1.1.1.jar". I don't need logging, maybe > > someone knows a way to disable it? Or, if not, how can i get this to > > work. The main JAR-Archive has enough rights. > > I tryed also to sign the commons JAR, but it doesn't help either. > > > > Any suggestions are welcome. > > > <snip/> > > Please double check that you are indeed using the 1.1.1 jar. If you are, > then post a fuller trace. A similar issue was fixed [1] and released [2] in > 1.1.1. > > -Rahul > > [1] http://issues.apache.org/jira/browse/LOGGING-106 > [2] http://commons.apache.org/logging/RELEASE-NOTES.txt > > > > Steffen > > > > >
