meta-api -> The core API for interpreting meta info meta-spi -> Interfaces for reading/writing meta info meta-impl -> Different readers and writers for meta info, and a verifier meta-tools -> ANT additions to generate meta-info, etc. meta-plugin -> Maven plugin to directly work with meta-info
Overall I don't have a problem with this. However, I do have a few questions as it is now defined:
1) What, precisely, is the difference between a Service and a Type? - A Service defines contracts for client/component communication - Programmatically what is the difference?
2) Why are the readers and serializers for types and services separate
and distinct?
- Aren't services a function of what is exported by a type?
- Are their information recorded separately, hense lending support to
the notion that an interface defines a service?3) Don't we want many readers, but only one official writer? - Do we want XML (safe between JRE changes)? - Do we want Serialization? - Do we want something else intirely (i.e. bytecode embedding)?
4) How about allowing for extensions to be incorporated into the reader/writers/ verifiers?
5) What do we have separate readers/writers for services and types? - I believe it would be cleaner to have one for each.
--
"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]
