Sure, no problem.
You might want to consider moving the plugin related code to its own package, perhaps to o.a.l.plugin.
At 21:27 21.11.2002 -0800, you wrote:
> I did not make any > changes in the code to make the Hierarchy actually send all the > messages at > the correct time. I leave that to someone else. It might need to be > thought through some.That actually sounds worse than it is. The Hierarchy has all the code in place to send the messages to registered listeners, and it does send messages for reset and shutdown. However, I did not change all the other code to call the appropriate fireXYZ() methods at the right times. So, for example, I have not modified any of the configurator classes to call the fireConfigurationChangedEvent() method on the LoggerRepository being configured. -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
