David,
IMHO this should be clearer in the specification. Actually, since the
remote services 'API' is basically a set of service properties, I
suggest that for each service property it be clearly stated (table?)
what the appropriate provider behavior is when the property is not set.
Thanks,
Scott
On 9/24/2010 1:10 AM, David Bosschaert wrote:
Hi Markus,
If service.exported.configs is not specified, the Distribution
Provider should use its default mechanism.
> From section 122.5.1:
• service.exported.configs – (String+ ) A list of configuration types
that should be used to export
this service. Each configuration type represents the configuration
parameters for an Endpoint. A
Remote Service Admin service should create an Endpoint for each
configuration type that it supports
and ignore the types it does not recognize. If this property is not
set, then the Remote Service
Admin implementation must choose a convenient configuration type that
then must be reported
on the Endpoint Description with the service.imported.configs
associated with the returned
Export Registration.
Hope this helps,
David
On 24 September 2010 08:35, Markus Alexander Kuppe
<[email protected]> wrote:
Hi,
as part of an ECF bug [0], the ECF team currently discusses how
distribution provider are expected to behave WRT
"service.exported.configs" not set. In 13.2.1 the Remote Service part of
the spec just states (p. 11):
"If no configuration types are recognized, the distribution provider
should create an endpoint with a default configuration type except when
one of the listed configuration types is<<nodefault>>."
What is the intended behavior if an exported service only has the
service property "service.exported.interface" set and nothing more?
Regards
Markus Alexander Kuppe
[0] https://bugs.eclipse.org/326053
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
