Berin Loritsch wrote:
Berin Loritsch wrote:
Stephen McConnell wrote:
Berin:
I'm confussed - I don't understand what this would provide nor why you think its an important piece. Based on the current model you would use tools to generate a Type defintion - the tool maps between an input format and a Type. A Fortress tool could read in whatever and generate the Type directly. Code inside Fortress would then code against the meta-info API.
Fortress has more than one stream associated with the type information.
Extensions will have their own file formats (the two I listed are examples).
I believe it is important to have one set of tools for all containers.
That is the purpose of separating out the Meta model and working on it in
scratchpad.
Ok. I have made a first cut at this, which will allow you to update
your writers to address the @todo regarding serializing the configuration/
default configuration info.
Berin:
I figure you can do everything you want with the following service.
public interface MetaInfoLocator
{
InputStream getInputStream( Type type, String extension)
throws MetaInfoException;
OutputStream getOutputStream( Type type, String extension)
throws MetaInfoException;
}Can you confirm. I would like to revert the changes the changes you added asap in favour of defining this as a service under the SPI package.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
