How adapter id is generated

aozarovaozarov Member Arie OzarovOrganization: hi5 NetworksProject: SOA ✭✭
Hi,

What is the logic that an icegridnode applies when generating a configuration to create an adapterID (if one was not explicit specified) and when using an IceBox?

From what I can see it is:

IceBoxName + "." + adapter_name + "." + service_name

Is that correct and can I assume that it is part of the protocol/api and is not
going to change in the future?

Also, why does it add the service_name?
What happens in the case of multiple services using/sharing the same adapter?

Thanks.

Comments

  • benoitbenoit Rennes, FranceAdministrators, ZeroC Staff Benoit FoucherOrganization: ZeroC, Inc.Project: Ice ZeroC Staff
    Hi Arie,

    The default adapter ID for an IceBox service object adapter is "${server}.${service}.<adapter name>" where ${server} and ${service} are substituted with the server ID and service name. This shouldn't change.

    The service name is added to avoid clashes if multiple services declare an object adapter with the same name with different communicators. If multiple services somehow share the same object adapter, only one of them should declare the adapter in its XML descriptor and you can define manually the adapter ID to ensure it doesn't contain the service name.

    Cheers,
    Benoit.
Sign In or Register to comment.