"Stephen McConnell" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Eike Stepper wrote: > > > "Stephen McConnell" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL > > PROTECTED] > > > >>Eike Stepper wrote: > >> > >> > >>>here they are: > >> > >>Umm .. looks ok. > >>Can you post the xinfo of the "app.Client1" component? Also, I would be > >>interested in seeing the log with "merlin.audit" set to 'true'. > > > > > > i've attached the log and here is the SocketConnector.xinfo: > > <snip> > > After looking at the audit info I think I understand what is happening. > The component [/app/Client1] has a single service provider assigned > for all of the service dependencies. The provider happens to be a > component component (a.k.a. container exporting multiple services). > > container:[/]) > children: > container:[/app]) > children: > container:[/app/net4j]) > --> [/app/Client1] > > When your listing the components returned from the service manager - you > basically invoking toString() on the proxy of the container. The > container proxy is delegating the toString() invocation to > DefaultProtocolManager resulting in the misleading log messages. This > is basically of side effect of the fact that composite proxies are > create as aggregates of the exported interfaces - when in fact it would > be better to construct a specific proxy corresponding to an identified > service dependency. > > I've referenced this thread together with some related noted under the > following issue: > > http://nagoya.apache.org/jira/browse/RUNTIME-34
from your answer i'm not totally sure who made the mistake. the concepts of nesting containers are a bit unclear to me. up to now i've found them to be the only means to provide multiple service-to-component mappings and i use them only for that purpose. is that ok? /eike for components i followed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
