You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by kujunguo kujunguo <ku...@gmail.com> on 2008/12/04 11:35:55 UTC

Does multiplicity mean the value number of target?

I specified the multiplicity to "1..1", but the target has two values.
According to the spec, it will conflict, but I passed the test.
Anything wrong with me?

 <reference name="bService" target="ServiceComponent2/MyService
ServiceComponent/MyService" multiplicity="1..1">          </reference>

Any responses are most appreciate!

Re: Does multiplicity mean the value number of target?

Posted by kujunguo kujunguo <ku...@gmail.com>.
Simon, I've opened a Jira bug for this issue:
https://issues.apache.org/jira/browse/TUSCANY-2720

2008/12/4 Simon Laws <si...@googlemail.com>:
>
>
> On Thu, Dec 4, 2008 at 10:35 AM, kujunguo kujunguo <ku...@gmail.com>
> wrote:
>>
>> I specified the multiplicity to "1..1", but the target has two values.
>> According to the spec, it will conflict, but I passed the test.
>> Anything wrong with me?
>>
>>  <reference name="bService" target="ServiceComponent2/MyService
>> ServiceComponent/MyService" multiplicity="1..1">          </reference>
>>
>> Any responses are most appreciate!
>
> I think the model processing should raise an error in this case. I think
> that's the direction OASIS is going in. I agree that the OSOA spec is not
> specific in this case. Can you raise a JIRA for this?
>
> Thanks
>
> Simon
>

Re: Does multiplicity mean the value number of target?

Posted by Simon Laws <si...@googlemail.com>.
On Thu, Dec 4, 2008 at 10:35 AM, kujunguo kujunguo <ku...@gmail.com>wrote:

> I specified the multiplicity to "1..1", but the target has two values.
> According to the spec, it will conflict, but I passed the test.
> Anything wrong with me?
>
>  <reference name="bService" target="ServiceComponent2/MyService
> ServiceComponent/MyService" multiplicity="1..1">          </reference>
>
> Any responses are most appreciate!
>

I think the model processing should raise an error in this case. I think
that's the direction OASIS is going in. I agree that the OSOA spec is not
specific in this case. Can you raise a JIRA for this?

Thanks

Simon