Hi, Adrian.
Thank you for reporting the problem and I'll look into this issue.
FYI: The best way to report an issue is to create a JIRA at
http://issues.apache.org/jira/browse/TUSCANY. You were lucky to get the
attachements pass through the mail as they are usually filtered out :-).
Thanks,
Raymond
----- Original Message -----
From: Adrian Mos
To: [email protected]
Cc: Olivier Abdoun ; Lionel Seinturier
Sent: Tuesday, November 06, 2007 7:32 AM
Subject: Problem with dependency resolution when using promoted references
and services
Hi guys,
We are working on an SCA application involving multiple levels of nested
composites and we ran into a problem when wiring promoted references to
promoted services.�
Basically we are getting the following exception (see bellow for partial
stack trace)
org.osoa.sca.ServiceUnavailableException: No service invoker is available
for reference i (bindingURI=O2Component/O2Component/O1Component
operation=get).
at
org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:192)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addBindingInterceptor(RuntimeWireImpl.java:214)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:156)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:97)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:190)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:124)
at $Proxy5.get(Unknown Source)
at foo.B.get(B.java:14)
...
...
We have reproduce the problem in a sample app that has the composites as
illustrated in the figure below.�
Attached you'll find the tar.gz of the project, you can generate the eclipse
project for it by running mvn eclipse:eclipse. You can see from the JUnit
test that the problem occurs when trying to bind the promoted reference of
the O3Component (corresponding to the O3Composite) to the promoted service
of the O2Composite. Note that if we do not try to bind a promoted reference
to this service or if we do not promote a composite reference (but rather
just a component reference), the problem does not occur.�
It would be great of you could try this out and let us know if the problem
is in the way the composites are written or if it's a Tuscany implementation
issue.�
Thank you,
Adrian Mos & Olivier Abdoun (INRIA)
---------------
Adrian Mos
ObjectWeb Project
SOA Technical Lead
[EMAIL PROTECTED]
+33 4 76 61 54 02
INRIA Rhone-Alpes
655 avenue de l'Europe -�Montbonnot
38 334 Saint Ismier Cedex France
Hi guys,
We are working on an SCA application involving multiple levels of
nested composites and we ran into a problem when wiring promoted
references to promoted services.
Basically we are getting the following exception (see bellow for
partial stack trace)
org.osoa.sca.ServiceUnavailableException: No service invoker is
available for reference i (bindingURI=O2Component/O2Component/
O1Component operation=get).
at
org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvid
er.createInvoker(RuntimeSCAReferenceBindingProvider.java:192)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addBindingIntercept
or(RuntimeWireImpl.java:214)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChain
s(RuntimeWireImpl.java:156)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains
(RuntimeWireImpl.java:97)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocatio
nChain(JDKInvocationHandler.java:190)
at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke
(JDKInvocationHandler.java:124)
at $Proxy5.get(Unknown Source)
at foo.B.get(B.java:14)
...
...
We have reproduce the problem in a sample app that has the composites
as illustrated in the figure below.

Attached you'll find the tar.gz of the project, you can generate the
eclipse project for it by running mvn eclipse:eclipse. You can see
from the JUnit test that the problem occurs when trying to bind the
promoted reference of the O3Component (corresponding to the
O3Composite) to the promoted service of the O2Composite. Note that if
we do not try to bind a promoted reference to this service or if we
do not promote a composite reference (but rather just a component
reference), the problem does not occur.
It would be great of you could try this out and let us know if the
problem is in the way the composites are written or if it's a Tuscany
implementation issue.
Thank you,
Adrian Mos & Olivier Abdoun (INRIA)
---------------
Adrian Mos
ObjectWeb Project
SOA Technical Lead
[EMAIL PROTECTED]
+33 4 76 61 54 02
INRIA Rhone-Alpes
655 avenue de l'Europe - Montbonnot
38 334 Saint Ismier Cedex France
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
