Curt,
I has another look at the changes you posted with bug #32478 and will be studying it closely tomorrow. I was wondering if you could think of a use case where replaying the events would be of a significant advantage as compared to the two passes approach. Anyway, I very much like the idea of replaying the events and intend to commit your code there aren't any hiccups that surface at the last minute.
At 05:34 PM 12/1/2004, Curt Arnold wrote:
On Dec 1, 2004, at 3:52 AM, Ceki G�lc� wrote:
One approach would be to try to stack configuration actions in a list, but I think that would be pretty complicated. It appears that the Joran configurator ignores any character content (other than within attribute). It should be fairly simple to parse the document and create a list of start and end element events, then replay the events into the Joran configurator.
You could do that but why bother?
I hate doing something twice. There is also the unlikely possibility that the content may change between requests (say if configuration file generated on URL access contained the current system time or some tracking number).
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
