On Sat, 25 Aug 2001, Mircea Toma wrote:
>
> ----- Original Message -----
> From: "giacomo" <[EMAIL PROTECTED]>
> To: "Avalon Development" <[EMAIL PROTECTED]>
> Sent: Saturday, August 25, 2001 9:54 AM
> Subject: LogKitManagement
>
>
> >
> > Dear all
> >
> > I've committed the updated Component Management System in Excalibur that
> > work together with the recently written LogKitManagement System.
> >
> > The fact that the ExcaluburComponentManager is in the java directory
> > where as the LogKitManagement classes were still in the scratchpad
> > directory I had to move the LogKitManagment classes into the java area
> > because the build procedure does not work together when you have to mix
> > those areas.
> >
> > I have tested them quite alot (jswat and some batches) and there is a
> > test based on ExcaliburTestCase to see it working I propose to move the
> > LogKitManagement classes into the java tree.
> >
> > I don't know the release schedule for Excalibur but I would like to see
> > the LogKitManagement making it into the next release which can be
> > integrated into Cocoon 2 before the the next release will go live.
> >
> > Right now I'll write the xdocs for the LogKitManagement which I'll
> > commit soon.
> >
> > So, the hard part has just started. Some more LogTargetFactories have to
> > be written to make the system more handy ;)
>
> I would like to do that! I can start with RotatingFileFactory,
> JMSTopicTargetFactory, JDBCTargetFactory .... because I need then anyway!
I think it's best to have one Factory for a media target (I/O, JMS,
JDBC). So, the FileTargetFactory should be able to be configured to
create rotating or not targets, if rotating then by size or time or
both, etc.
What do you think?
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
