Eric Pugh wrote:
public void initialize() throws Exception
{
// initBundleNames(null);
defaultLocale = new Locale(defaultLanguage, defaultCountry);
Localization.setLocalizationService(this);
This breaks Avalon principle of inversion of control, and managed components. Static singletons are very evil, and _strongly_ discourage in Avalon and many other managed environments.
You should probably have Localization as an interface and have 'this' class implement it.
That would also not require any resolve() to be called. The resolve() will be called when other components requests the Localization via the ServiceManager.
I starting to have the feeling that too much 'advanced features' has been discussed in the users@ list, and new ones get confused after seeing all these advanced tactics.
Almost always the solution is much simpler than one first thinks.
First principle, let Merlin manage the components. Few cases requires 'manual' handling of component instances. So, the component needs to be declared properly, and the clients needs to look it up via the service manager. Only after 'proving' that this isn't feasible, one need to resort to more complex manuovers.
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
