Re: [sca-j] Q about POJO introspection rules

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

On 3/17/2011 7:27 AM, Mike Edwards wrote:
>
> Anish,
>
> The introspection rules take the simple view - and it is the simple name
> that is used when introspecting
> a class for the interfaces it implements, not the fully qualified name.
>
> So in your example of a class implementing com.foo.DishWasher and
> com.bar.DishWasher
> you'd end up with 2 service names "Dishwasher" which would cause an error.
>
> To solve this you'd have to annotate the class concerned with an
> @Service annotation and spell out the
> names that you want used.
>
>
>
> If I recall correctly, this was debated at the time the rules were
> created and the solution I've outlined was deemed
> acceptable for what is a corner case (note: the interfaces have to have
> @Remotable applied for any of this to
> work, so it seems only a small step to require the implementation class
> to have @Service applied).
>

Got it. Thanks for the reminder.

-Anish
--

> Yours, Mike
> ------------------------------------------------------------------------
> Dr Mike Edwards 	Mail Point 137, Hursley Park 	
> STSM 	Winchester, Hants SO21 2JN
> SCA & Services Standards 	United Kingdom
> Co-Chair OASIS SCA Assembly TC 		
> IBM Software Group 		
> Phone: 	+44-1962 818014 		
> Mobile: 	+44-7802-467431 (274097) 		
> e-mail: 	mike_edwards@uk.ibm.com 		
>
>
>
>
>
> From: 	Anish Karmarkar <Anish.Karmarkar@oracle.com>
> To: 	OASIS Java <sca-j@lists.oasis-open.org>
> Date: 	16/03/2011 23:40
> Subject: 	[sca-j] Q about POJO introspection rules
>
>
> ------------------------------------------------------------------------
>
>
>
> I was looking at the POJO spec in the context of resolving issue 228.
> Section 8.1, line 572 of the POJO spec [1] addresses the name of the
> introspected service and says the following:
>
> "name attribute is the simple name of the interface or the simple name
> of the class"
>
> Service names have to be unique within a component. In the case where
> the class implements multiple remotable interface, how does the 'simple
> name' meet this uniqueness restriction?
>
> For example, what happens if my implementation class implements two
> remotable interfaces: com.foo.DishWasher and com.bar.DishWasher. You
> can't have two services called 'DishWasher' for the same component. Am I
> missing something OR is this a bug and "s/simple name/fully qualified
> name/" (for interfaces).
>
> -Anish
> --
>
> [1] http://docs.oasis-open.org/opencsa/sca-j/sca-javaci-1.1-spec.pdf
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> /
> /
>
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU/
>
>
>
>
>
>