Thank you, Kevin! That explains it and confirms we have the correct
behaviour.
Perhaps we should update the JavaDoc (for
createSelfReference(java.lang.Class businessInterface)) to NOT say
"default service" for that may mis-lead folks to think that we can define
a default service somehow ..
-
I meant to say:
... an exception is expected if you use the first version of the
createSelfReference API to create a ServiceReference to a component
offering multiple services.
--
Kevin
On Fri, Apr 4, 2008 at 10:24 AM, Kevin Williams <[EMAIL PROTECTED]> wrote:
> Hi Yee-Kang,
>
> Further down i
Hi Yee-Kang,
Further down in the specification is:
435 The second variant, which takes an additional serviceName
parameter, *must* be used if the component
436 implements multiple services.
So, an exception is expected if you employ the first version of the
createSelfReference API.
--Kevi
Hi Everyone,
V1 of the Java Annotations & APIs Spec described these two methods as
follows:
createSelfReference(Class businessInterface) ? Returns a
ServiceReference that can be used to invoke this component over the
designated service.
createSelfReference(Class businessInterface, String servi
