Well, sure, it just has to be in the applet's classpath. Which is a set of resources on the server (you specify them in the HTML element which describes the applet). One of those resources would be the applet's jar, assuming you decided to put the applet in a jar. There can be others.
Originally posted by Tom Katz:
Is there anyway to not include the log4j.properties file in the applet's jar itself? So that the log level can be configurable at the server, and those configuration changes affect the log level of the applet code?
passing that log level/priority/filename on the server TO the applet code that runs on the client. I"ve tried through applet params,
Amateurs built google. Professionals built the titanic. We can't find the guy that built this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton