Berin Loritsch wrote:
Stephen McConnell wrote:
What I'm pointing out is that the Merlin usage of manifest information has nothing to do with the registration of type or service information. It has everything to do with structual dependency management done in a way that is 100% consistent with the java operational extensions specification.
Really? Now you peaked my curiosity, and I want to know more. Got a
URL that explains how things work, or can you give a brief overview?
The specification is here: http://java.sun.com/j2se/1.4.2/docs/guide/extensions/versioning.html
The implementation is in merlin/extension and merlin/extension-spi.
http://avalon.apache.org/sandbox/merlin/api/org/apache/avalon/extension/package-summary.html
http://avalon.apache.org/sandbox/merlin/api/org/apache/avalon/extension/manager/package-summary.html
http://avalon.apache.org/sandbox/merlin/api/org/apache/avalon/extension/manager/impl/package-summary.html
Thanks for the reading material ;P
I'll probably have some more questions later.
Merlin (like Phoenix) colocates meta-info descriptors with the class they are describing - e.g. <classname>.<extension>. Phoenix accesses this inforation on demand based on static descriptors. Merlin scans jar files for type and service descriptors, loads then in a repository, and uses this repository to provide information about available component solutions to higher level services.
And how does this affect startup times? I think one of the chief concerns with the "Attributes Proof of Concept" thread was the startup time if we went through all the public classes and discovered the meta info at that time.
--
"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]
