[jira] Resolved: (RUNTIME-31) Components not initialized when got from ServiceManager

     [ http://nagoya.apache.org/jira/browse/RUNTIME-31?page=history ]
     
Niclas Hedhman resolved RUNTIME-31:
-----------------------------------

    Resolution: Won't Fix

Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net

> Components not initialized when got from ServiceManager
> -------------------------------------------------------
>
>          Key: RUNTIME-31
>          URL: http://nagoya.apache.org/jira/browse/RUNTIME-31
>      Project: Merlin Runtime
>         Type: Bug
>     Versions: 3.3.0
>  Environment: All
>     Reporter: syvalta
>     Assignee: Stephen McConnell

>
> Getting component from ServiceManager doesn't initialize the component. For example:
> m_component = (Component) m_manager.lookup(Component.class.getName());
> After that component should be initialized (i.e. life-cycle methods called), but actually it is initialized only when it is actually accessed (for example m_component.doSomething()). For example, if a event listener is set up in initialize(), it actually won't be listening any events. There might be some reasons for lazy initialization, but as a user I see it as a source for problems difficult to track.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira