At 11:59 PM 6/16/2004, you wrote:
JMS+Webstart may be a little more marginal, but I know of at least 2 people that would like it to work... :) At any rate it is _annoying_ me no end when something should work, and I can't get to work. Call me stubborn, but it's these "why can't I get it to work" situations that make me want to do it any way. Call it an Australian stubborness thing. We hate to lose. :)Web start might not be a marginal deployment scenario, but Webstart+JMS probably is. How many people will still use webstart once 1.3 is released?
I imagined something of the sort. :-)
You are right to observe that the same problem with occur with JDBC as well. You could allow the user to set the TCCL as an *option* and never by default. I still think that by setting our own classloader we trying to do something Web-start is not designed for. However, if you are willing to do the work, I would not want to spoil the fun.
Is there any way you could think of that I could tweak the JoranConfigurator so that I can tell it which ClassLoader to use? Does that make sense? When Chainsaw starts up, it checks if there is a standard log4j.xml file that the user wishes to use for Configuration, and if someone wants a JMS/DB Receiver to load each time Chainsaw launches, then JoranConfigurator will need to be told to use the PluginClassLoader. I don't mind making the change, but just would love your thoughts on the matter.
Have a look into at the o.a.l.helpers.Loader class. All log4j components use (or should use) the Loader class to load components. Maybe you can tell the Loader class to use your PluginClassLoader. The name PluginClassLoader is a little misleading because it is not just plugins but all log4j components such as Layouts and Appenders etc.
You can easily write a joran action which creates an auxiliary classloader to be used in conjunction with o.a.l.helpers.Loader for the length of the Joran configuration session. We can even imagine making using an instance of the Loader class which relies on that auxiliary classloader.
It's kind of a big and intrusive change but one that I am confident should work as long as the config file is customizable by the end user. So, is the log4j.xml file part of the webstart files or is it something supplied by the user?
cheers,
Paul Smith
-- 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]
