On Monday 28 April 2008 20:29:10 Ruben Smits wrote:
> Maybe the deployer should also offer the opposite:
>
> creating a CorbaServer of a component loaded by the deployer, so remote
> tasks can connect to it?
Do you have an idea how to indicate this from a user's POV ? Would the
cdeployer create a server for all components by default or would you define a
property (and in which way) ?
Peter
[Bug 534] [Project] deployer can not connect to CORBA components
On Tuesday April 29 2008 10:32:24 Peter Soetens wrote:
> On Monday 28 April 2008 20:29:10 Ruben Smits wrote:
> > Maybe the deployer should also offer the opposite:
> >
> > creating a CorbaServer of a component loaded by the deployer, so remote
> > tasks can connect to it?
>
> Do you have an idea how to indicate this from a user's POV ? Would the
> cdeployer create a server for all components by default or would you define
> a property (and in which way) ?
I would define a property in the deployers component xml-struct that indicates
if a server has to be created for the component.
Ruben