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?
I thought that Merlin had entries like this:
Name: com.mycompany.MyService Service: True
Name: com.mycompany.impl.MyComponent Type: True
Not since Merlin 1.0. (a.k.a. a not since a very long time)
Wow, been busy, huh?
So how does Merlin address the type/service registration part of the equation?
Merlin uses manifest information to establish the physical dependencies that one jar file has on another jar files, and from that, recusively builds a tree of dependencies taking into account the dpendencies of the dependent jars, etc. This is at a totally different level of abstraction to the question of where and how services, types or attributes are registeered. Instead - its about the management of the physical dependencies that a jar file has.
Ok, pretty much part of what I outlined in my RT on classloader repositories.
Which standards are you referring to?
Merlin: Manifest entries Fortress: JAR Services entries
Question remains - which standards are you referring to (URL to spec- etc.)?
At this point it is a moot point, it is clear that I am woefully behind the times with how Merlin works with JAR files.
--
"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]
