My first container will basically poll a group of spool directories and when a file is move into one of the watched directories, it will ask a component to convert the file to a different format in another spool and moved the original to a third spool (archive).
A bit more information, I will probably use JNDI for the spools. The polling interval/controller could be cornerstone scheduler. The converter might work on streams or files and I might introduce caching later.
My initial design has these three main components: Scheduler - DirContextMonitor - FormatConverter
Scheduler just invokes DirContextMonitor::trigger() at appropriate times.
DirContextMonitor does a single poll of the spool per trigger() and if it locates an entry invokes FormatConverter::convert(), on success it moves the entry to the archive directory.
FormatConverter reads the entry, converts it and writes the converted entry to a destination.
I realise there are few extra components related to scheduling and pool management.
Basically, does this look sensible? Deciding where to make classes, components and blocks at the moment is my biggest mental hurdle.
thanks, Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
