Michael Laccetti wrote:
Okay, that got it up and running - I was wondering where that is documented -
I've been reading the Tuscany in Action MEAP and the online docs, but didn't
seem to stumble across that (important) tidbit.
________________________________________
From: Simon Nash [[email protected]]
Sent: August-10-09 5:16 PM
To: [email protected]
Subject: Re: Service not found
Hi Michael,
The name of your service in the component definition should
be OdfWebService (the unqualified name of the Java interface),
not ODF.
Simon
Hi Michael,
Sections 2.2.1 and 2.2.3 of the Tuscany in Action MEAP talk about
service naming but not in quite as clear and direct a way as they
could. The missing pieces are 1) the naming rules when there is
no @Service annotation, and 2) the importance of using the same
names in the component definition as are used in the implementation
and the component type. We will address this in the next draft.
The other place you should be able to find this information is in
the osoa.org SCA specs. For the case with @Service specified, the
naming rule is stated in section 1.8.17 of the Java Common Annotations
and APIs spec, with some examples in section 1.2.1.1 of the Java
Component Implementation spec. However, I don't think either of
these specs say what name is used when @Service isn't present.
This omission is corrected in the OASIS version of the Java Component
Implementation spec (see section 8.1).
Simon
