Raymond Feng wrote:
Hi,
I'm very sure if it's a good idea to add "provideNameServer" flag into
the <binding.corba> which will be affecting users at the programming
model level. What would happen if two SCA services with binding.corba
set the flag to true? Depending on the environment, the name server can
be started/stopped differently. For example, the JEE app server usually
starts/stops the CORBA name server with the server. We can also run
tnameserv or orbd commands to start the name server.
Thanks,
Raymond
Folks,
I tend to agree with Raymond on this.
Having to provide a name server is really part of the configuration of the Tuscany runtime, not
configuration of an individual binding.
It would be valid for a particular binding to indicate that it needs a name server and will not run
without one - this is quite close in concept to an implementation intent - @requires="NameServer"
This would then fail to run on a Tuscany runtime that does not have a name
server available.
The configuring of a nameserver should be left to configuration of the node(s) that are started to
run the composite(s).
Yours, Mike.
