[EMAIL PROTECTED] wrote:
Hi,
I only want to know the difference between using DefaultServiceManager (ex-DefaultComponentManager)
from Avalon Framework and using ExcaliburComponentManager from Avalon Excalibur ?
When shall I use DefaultServiceManager and when is ExcaliburComponentManager better ?
Umm - not a simple question!
DefaultServiceManager is nothing more that a utility class that programmers can use to construct a ServiceManager instance that they can use to pass to a component. This typically occurs when you are writing code in which you are deploying components. ExcaliburComponentManager (ECM) is something related but at the same time is very different. ECM adds some extract semantics to the lookup operation to support returning of selectors and basically executes relative to a configuration in which assignes shorrt names to component types. ECM is being replaced by a cleaner implementation - Fortress. Fortress is a light-weight container that delivers the same functionality as ECM but does with a improved container/component seperation.
Short answer - DefaultServiceManager and ECM not not really comparable. ECM is compparable with Fortress.
Is there any documentation about it ?
I suggest you take a look at the Fortress site:
http://avalon.apache.org/excalibur/fortress
Cheers, Steve.
Thanks,
Cecile
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
