Hi,
here are details about proposition patch under [1]. Please take a look
at comments inline.
Raymond Feng wrote:
> 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.
This solution only could create one TNS on fixed port. Don't we want
this module to provide TNSs for every CORBA service bindings?
Jean-Sebastien Delfino wrote:
Wojtek Janiszewski wrote:
...
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?
Makes sense to me.
A variation of this, maybe simpler could be to have host-corba-jse-tns
just boot the name server, so as a user, with host-corba-jse I get an
ORB, with host-corba-jse + host-corba-jse-tns I get an ORB + a name server.
Makes sense? if not, then again your proposal sounds good to me too.
Your proposal seems to be more flexible than mine.
I don't want to mess in svn too much so I've published my proposition as
patch, which can be found under [1]. Here's how the host-corba-jse-tns
works:
1. It should be used together with host-corba-jse module
2. Both host-corba-jse and host-corba-jse-tns are formed in something
like invocation chain. host-corba-jse-tns registers in chain with
highest priority so its methods always executes before host-corba-jse
methods. This chain can be extended easily by adding other CorbaHost
modules.
3. host-corba-jse-tns for method registerServant creates TNS, method
unregisterServant stops TNS (if no other service binding is using it).
4. No changes were made to host-corba-jse so after removing
host-corba-jse-tns dependency host-corba-jse acts like before.
What do you think?
Thanks,
Wojtek
[1] - https://issues.apache.org/jira/browse/TUSCANY-2357
