Hi Simon,
please check out the files I uploaded to https://issues.apache.org/jira/browse/TUSCANY-2281. It works in my environment J Bye, Daniel Von: Simon Laws [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 17. September 2008 13:01 An: user@tuscany.apache.org Betreff: Re: Multiplicity issue [TUSCANY-2281] On Wed, Sep 17, 2008 at 10:21 AM, <[EMAIL PROTECTED]> wrote: Hi Simon, I guess this is the issue Raymond mentioned: http://www.osoa.org/jira/browse/JAVA-9. I don't know if my SCA/Tuscany knowledge is sound enough to be able to provide such an implementation, but I will give it a try. So expect frequent rookie questions J Bye, Daniel Von: Simon Laws [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 16. September 2008 20:20 An: user@tuscany.apache.org Betreff: Re: Multiplicity issue [TUSCANY-2281] On Mon, Sep 15, 2008 at 11:00 PM, Simon Nash <[EMAIL PROTECTED]> wrote: Raymond Feng wrote: Hi, This is an interesting situation: The SCA APIs defined by OSOA have some deficiencies which are being fixed under OASIS. Now the question is how we branch the development streams to support the different level of the SCA specifications. Should we start to look into the possibility to create a 2.0 branch to contain the upcoming work to support OASIS SCA specs and other disruptive changes? The spec change to resolve OASIS issue JAVA-9 is upwards compatible. It requires the addition of two new methods on org.osoa.sca.ComponentContext. There is no need to create an incompatible branch for this change. Simon Thanks, Raymond -------------------------------------------------- From: <[EMAIL PROTECTED]> Sent: Monday, September 15, 2008 8:53 AM To: <user@tuscany.apache.org> Subject: Multiplicity issue [TUSCANY-2281] Hi all, I just wanted to ask about the state of JIIRA https://issues.apache.org/jira/browse/TUSCANY-2281. Am I the only one that misses this feature ? Are there any plans if/when/how this may be implemented ? Can I somehow contribute ? (I could provide a test case if that helps) Bye, Daniel Hi Daniel I have to admit that I haven't looked at this since the last time we spoke on this. I looks, from what Simon says, that we should be able to solve this by adding a couple of new methods to the CompnentContext which would live quite happily next to what is there already. Are you interested in providing an implementation of these? If so we can just commit your patch. Simon Hi Daniel Yep, that's the JIRA. Re. questions. Ask away ;-) Simon
