Berin Loritsch wrote:
Having multiple containers is not only workable, but they are critical to+1 (and ready to contribute)
the process of finding out what needs to be in framework and what is
container specific. It will also help address the issue of how to handle
things such as component extensions in a cross platform way, and how
to make the component still work if extensions are not used.
Considering that Stephen and I (primary developers on the two competing
containers in Excalibur) have proven that we are able to work with each
other, I don't think we will run into any serious or unresolvable problems.
I believe that using metadata is the way to go, but I am not convinced that
either Meta or Info are the best way to express it. If we can come up with
one specification for how the meta information is *stored*, we can have
multiple implementations like Meta and Info that make reading the metainfo
easier.
I would propose working with the Jakarta Commons Clazz project to help
implement class/method attributes.
I have been digging into the clazz package to get to understand it a little better. My initial impressions are that the relationship between the Avalon meta (lowercase) related work is complimentary - in fact it would provide several features over and above the current implementations.
Any suggestions on where this should/could be located?
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
