Stephen McConnell wrote:
>
> Berin Loritsch wrote:
>
>> --I don't have a clear picture of
>> how things get instantiated or how components get resolved.
>> Sure there is the markup, but as far as I can see, the decision
>> process over which implementation to provide to a component
>> interface is black magic.
>
This is detailed under the "Assembly" topic in the documentation. Given
a situation with multiple candidate service providers, a service
selector is established. The default selector can be overriden,
however, the default selector makes it very easy for the assembler to
ensure that the appropiate service is bound. The default selector
selects services based on a degreee of "explicitness" - if you declare a
componet in a container its an explicit component, whereas component
profiles supplied in a jar file (refered to as packaged profiles) don't
rank so highly. At the lowest end of the spectrum is the implicit
profile - a profile constructed by Merlin based on what it can figure
out by itself.
This is detailed under the following page:
http://home.osm.net/doc/merlin/assembly.html
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
