On Sat, 2004-01-17 at 03:09, Mathews Julien wrote: > But Fulcrum components in their present form ( the new ones ) must be > compatible to some Avalon standard/pattern. What standard is that ? ECM, > Fortress or Merlin ?
The standard is the Avalon Framework. However, for better or worse, the Avalon Framework is silent on a number of issues. One of which is the naming pattern for components (ie, what do you use for ServiceManager.lookup(String name)). Originally, Avalon was not about containers, it was about the framework. Several different container implementations have been available and each decided on it's own semantics, though there were similarities. See: http://wiki.apache.org/avalon/ServiceManager http://wiki.apache.org/avalon/ContainerStory for some more background. Thing is, Merlin departs somewhat from the previous lookup methods. That's not necessarily a bad thing. In fact, Merlin offers a very consistent set of contracts. But it does cause some issues about doing things the "ECM/Fortress/Phoenix" way vs. the Merlin way. Consequently, the "standards" are changing and aren't quite complete. -- jaaron <http://jadetower.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
