Preferably, what I'd want to do is: 1) get the default override as described in the manual to work 2) do manual programmatic configuration
2) I can do, but I'm not sure why 1) isn't working.
The reason 1) didn't work was because log4j was not signed. Therefore it could not read the system property, and hence went ahead with the default initialization procedure.
So, in order to get minimal number of connections with log4j in applets you need to do the following:
1) Sign the applet. This is necessary in order to set the system property
2) Add a static block in the applet class which sets the system property "log4j.defaultInitOverride" to "true", and configures log4j manually. File-based configuration is no good, since it results in attempts to load *BeanInfo classes due to the introspection mechanism used
3) Sign log4j.jar
After that it works great!
As you can see, a lot of the above would be simplified if there was another way to override the default initialization procedure besides using a system property. Using system properties in an applet is generally impossible unless you sign the jars.
/Rickard
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
