+1 to fix it per the OASIS resolution. I don't see this as a breaking change
as it only refines/adds additional methods to the API.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[EMAIL PROTECTED]>
Sent: Thursday, May 01, 2008 7:12 AM
To: <[email protected]>
Subject: [DISCUSS] SCA API extensions based on OASIS bug fixes Re: [jira]
Created: (TUSCANY-2281) How to create ServiceReferences for references using
multiplicity="1..n"
On Wed, Apr 30, 2008 at 12:13 PM, Daniel Stucky (JIRA) <
[email protected]> wrote:
How to create ServiceReferences for references using multiplicity="1..n"
------------------------------------------------------------------------
Key: TUSCANY-2281
URL: https://issues.apache.org/jira/browse/TUSCANY-2281
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.2
Reporter: Daniel Stucky
At the moment it is not possible to create ServiceReferences for specific
targets of references with multiplicity="1..n".
See the mailing list for details:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg03024.html
A quote from Simon Laws' answer:
"The OASIS TC has proposed a solution to this issue (
http://www.osoa.org/jira/browse/JAVA-9) but this isn't part of the API we
have implemented as we have taken the V1 API. Can you raise a JIRA for
this
as I can't see one already and at least in that way we can track it."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
The lack an SCA defined interface on the ComponentContext to allow for the
retrieval of multiple service references, in the case where the
multiplicity
is greater than one, has been noted by OASIS (
http://www.osoa.org/jira/browse/JAVA-9). This is clearly an omission from
the OSOA version of the specs that we have implemented. As far as I'm
aware
there is no OSOA errata for interface updates for this one.
I'm raising this in reference to this previous thread (
http://www.mail-archive.com/[email protected]/msg29820.html). I
would like to fix this but it's an SCA API addition so fear that people
will
view this as a major change where we can't guarantee what the final
outcome
will be (although the OASIS JIRA is marked as resolved). Anyone care to
comment?
Simon
