Hi Bob
On Mon, Nov 17, 2008 at 7:43 PM, Maloney, Robert A
<[EMAIL PROTECTED]>wrote:
> Hi Simon,
>
>
>
> > Without the domain manager process you could use the configuration in the
>
> > database to generate the configuration into the right place in the composite
>
> > file so everything knows where everything else is. This would involved a bit
>
> > of automated XML editing.
>
>
>
> 1) What would the resulting composite file look like?
>
> Just a normal XML composite file but with the uri of the reference and
service binding set appropriately depending on where the service is
deployed. Do you need a particular binding in you're environment?
> 2) Automated XML editing such as StAX, not functionality related to the
> domain-management sample code?
>
> I was thinking that you could use code from the domain manager buy you
could just go in and just create the XML using a basic XML processor
> 3) In code, how would I differentiate between the services?
>
>
How you you normally differentiate between services. By name? Or are you
looking for more details e.g. IP address, what the capabilities of the
hosting machine is etc. If you went for a component with a multiplicity you
would end up with a reference such as
@Reference(name = "dReferenceArray")
public DComponent[] dReferenceArray;
So you could iterate over the references but not identify each target
service as such. The only thing you know is that all the services implement
the same interface. IIf you wanted to get meta-data about each node you code
add an interface to the node so you could ask for it.
>From you scenario description the initial static configuration could be
managed quite happily. The tricky piece is adding new nodes after the system
has started. We don't have an out of the box way at the moment on adding
reference to an already running service. I.e. it would be difficult to add
new worker nodes to the scheduler without stopping the scheduler. However we
could look at adding a service interface to the Scheduler that allows new
nodes to register references to themselves and extend the reference array in
that way.Would take a bit of experimentation.
