> -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2003 1:00 PM > To: Avalon Developers List > Subject: Meta Info Reading and Writing > > One thing that seems to be missing from the meta-info SPI library is the > separation from stream/persistence. The issue here is that some things > are always tracked in separate files. Examples include JMX extensions, > Configuration schemas, etc. > > Instead of assuming one file contains all the meta info, we should allow > the reader/writer to ask for a resource by changing the extension alone. > > For example: > > interface MetaInfoResource > { > InputStream getMetaInputStream( String extension ); > OutputStream getMetaOutputStream( String extension ); > } > > The Readers and Writers will be able to get all the different streams > that belong to the particular resource. It will also allow extensions > to load their specific information as necessary. > > I believe this is very important piece of the system we need. It will > also help me write the readers/writers for existing Fortress components.
I've also wondered why we're always using XML files and not something like Jakarta Commons Attributes [1], particularly once we have a standard AMTAGS implementation. If as a component developer I'm setting all my meta-info in tags and letting build tasks or goals handle the meta-info file creation, then why should I worry about XML files? The persistence is transparent to me. Meta-data: I can understand why this is XML, but meta-info could easily be kept in other formats. jaaron [1] http://jakarta.apache.org/commons/sandbox/attributes/index.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
