I think this would solve a lot. First, we could use *one* metainfo builder for all containers. That builder would be forward-compatible and container-agnostic. You could experiment as much as you wanted with new container features.
Essentially you prefer option 3: scrap Avalon Meta as it is now defined in sandbox, and use something more generic. In the absence of JSR 175, we need to look at something that will work in the mean time--perhaps a BCEL bound tool.
Excuse me, I just want to point another nice tool inspired in .net
http://attrib4j.sourceforge.net/
It's from Ted Neward and others. I don't know if this project is dead, but for sure it has a lot of "to do".
Good looking out. I think it is definitely in line with what we would like to do. It has a recent release (4/18/03), and I would rather work with them then develop something new here that does the same thing.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
