Hello Jake,
At 11:29 PM 3/22/2004 -0600, Jacob Kjome wrote:
Had this email rejected twice with the following error: "_we_don't_accept_email_with_executable_content_"
I tried attaching a .zip file containing the two files I am attaching now. Who the heck is considering .zip to be an "executable"???? How annoying! Anyway, read on.....
Unfortunately, the user list does not accept zip files.
At 02:47 PM 3/22/2004 +0800, you wrote:
One thing to note (which I just found out myself) is that the RepositorySelector interface has changed in Log4j-1.3 CVS. Might want to take a look at ContextJNDISelector in logging-log4j. Ceki modified it from the one that was in logging-log4j-sandbox. So, just beware that the ContextClassLoaderSelector in the sandbox will not work with Log4j-1.3. Here's the new method that needs to be implemented for 1.3...
public void setDefaultRepository(LoggerRepository def);
Ceki, if you are reading this, why the change to the interface? You had been pretty opposed to this before.
Also, why the change to the JNDI lookup in ContextJNDISelector to to be "java:comp/env/log4j/context-name" instead of "java:comp/env/log4j/logging-context" as it was in the sandbox? I realize that the sandbox is not official code, but it makes moving to Log4j-1.3 more difficult since anyone using the old one will have it configured to use "logging-context" (including me, of course). I think the javadoc still refers to "logging-context" not "context-name" in one spot, although the example provided says "context-name". If there is no real good reason to change the name, can it move back to "logging-context"? The new autoconfiguration looks interesting. Maybe my advice to Vance about configuration not belonging in the repository selector was premature. I'll have to try it sometime here. In any case, could you detail your reasons for the change to the RepositorySelector interface?
If the repository selector can be set dynamically from a configuration directive, then there must be a way for the component configuring the repository selector to configure and set the default repository, hence the new method. Moreover, the exact implementation of the default repository does not need to depend on the implementation of the repository selector.
As for backward compatibility, it is not guaranteed for code in the sandbox.
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
