> Yes, Fortress has its own set of standard context entries [1] (different
> from Merlin) and uses a different set of meta-tags (though similar in
> some respects).
But mappable. So rather than ask
"Well, why Merlin? Why not Fortress/Phoenix/MyNewSpecification?"
Why not implement the Merlin approach internally, and map to it based upon
the component's configuration? There is no reason why the container can't
load a component into an environment that provides a mapping between the
component's expectations and the container's implementation.
That preserves a rather low-overhead means to preserve ROI in existing
Avalon-based client code without sacrificing the ability to evolve the
container.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
