----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: "Avalon Development" <[email protected]>
Sent: Friday, September 07, 2001 11:49 PM
Subject: Re: DefaultLogKitManager not fit for Phoenix blocks?
> Hi,
>
> I haven't had a good look at it yet but yours and Eung-ju work didn't look
to
> be backwards compatible. I was thinking that I don't really want to break
> backwards compatibility yet (not before we change from alpha->beta for
> Phoenix) so maybe we can deprecate the old version and add a new element
name
> <logging/> ??
-0
> or attribute <logs version="1.1" /> ???
+1
> that marks one logging
> system as being the "new one" and one as being the old style. Thoughts?
... we can provide a XSLT transformation too (as Ant target), for a smoother
transition!
Mircea
>
> On Fri, 7 Sep 2001 14:50, Mircea Toma wrote:
> > Here is the diff for DefaultApplicationFrame that uses
> > DefaultLogKitManager. The server.xml (<logs>) configuration should be
> > changed accordingly. I guess I can change the DefaultEmbeddor to use the
> > DefaultLogKitManager too ("TODO: allow configurable priorities and
> > multiple logtargets").
>
> --
> Cheers,
>
> Pete
>
> --------------------------------------------------
> The fact that nobody understands you doesn't
> mean you're an artist.
> --------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
