We could have a separate module such as host-corba-jse-tns that contains a
ModuleActivator to start/stop the name server. If a test case or sample
needs to start/stop the name server automaitcally, we can just just add the
host-corba-jse-tns as a test/runtime dependency.
Thanks,
Raymond
--------------------------------------------------
From: "Wojtek Janiszewski" <[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2008 4:11 PM
To: <[email protected]>
Subject: Re: svn commit: r682203 - in /tuscany/java/sca:
itest/corba/src/test/java/org/apache/tuscany/sca/test/corba/
itest/corba/src/test/java/org/apache/tuscany/sca/test/corba/types/
itest/corba/src/test/resources/
modules/binding-corba-runtime/src/main/java/org/
Hi,
I've tried to make it similarly to binding.ws, where (as I understand)
servlet container can be spawned inside node or it can be provided by
environment (ie. deploying web app. in Tomcat). Idea also was to share
created name servers between service bindings, but now I agree that having
this flag in binding scope is not right.
Is there any place in Tuscany where we could move creating name server, or
we are leaving it to user?
I also thought about creating additional CORBA host ie.
host-corba-jse-tns, which would be similar to existing host-corba-jse, but
would always provide name servers for every service bindings. Does it make
sense? Would it be useful?
Thanks,
Wojtek
Mike Edwards wrote:
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.
