[
https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stucky reopened TUSCANY-2056:
------------------------------------
Hi Simon,
I did some modifications in my test and ran into another problem. The problem
does not occur with binding.sca, only with binding.ws.
This time I call method run() on Alpha. Alpha calls getRef() on Beta and gets
a reference to Gamma. Alpha then calls some methods on Gamma (it's an
iterator).This works fine. However, if I call method run() on Alpha a second
time after the first one completed I get an exception. Here is the console
output:
Starting ...
14.03.2008 15:25:47 org.apache.tuscany.sca.http.jetty.JettyServer
addServletMapping
INFO: Added Servlet mapping: http://AFA-19393:8080/Beta
14.03.2008 15:25:47 org.apache.tuscany.sca.http.jetty.JettyServer
addServletMapping
INFO: Added Servlet mapping: http://AFA-19393:8080/Gamma
test.composite ready !!!
1st run ...
GammaImpl:GammaImpl(), conversationId=null
Gamma:start(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
value=id_0, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
value=id_1, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
value=id_2, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
value=id_3, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
value=id_4, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
Gamma:stop(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42
2nd run ...
GammaImpl:GammaImpl(), conversationId=null
Gamma:start(), conversationId=9631fa34-7ef4-4287-bb3b-b58fc519b7ee
GammaImpl:GammaImpl(), conversationId=null
Gamma:hasNext(), conversationId=a0484c5f-e5e1-4cb6-ad41-04a244a724ed
org.osoa.sca.ServiceRuntimeException: Target fault type cannot be resolved: null
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
at $Proxy14.hasNext(Unknown Source)
at services.AlphaImpl.run(AlphaImpl.java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
at $Proxy12.run(Unknown Source)
at launch.Launch.main(Launch.java:23)
Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: unknown
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
... 16 more
Caused by: org.apache.axis2.AxisFault: unknown
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:118)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:89)
... 17 more
Gamma:stop(), conversationId=a0484c5f-e5e1-4cb6-ad41-04a244a724ed
As you can see the "1st run" completes, using always the same conversationId
(06a8dc57-c174-40a5-8d26-576f11482d42).
In the "2nd run" there are two conversationIds used:
9631fa34-7ef4-4287-bb3b-b58fc519b7ee and a0484c5f-e5e1-4cb6-ad41-04a244a724ed.
Thanks for your help in advance.
Bye,
Daniel
> Conversation does not continue if a Service Reference is passed as a return
> value (not as a parameter) when using binding.ws
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2056
> URL: https://issues.apache.org/jira/browse/TUSCANY-2056
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
> Reporter: Daniel Stucky
> Assignee: Simon Laws
> Fix For: Java-SCA-1.2
>
> Attachments: test.zip, test.zip
>
>
> This problem is related to TUSCANY-2028. It is exactly the same use case, but
> instead of the default binding (sca) I now use binding.ws.
> And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I
> guess the fix that went into Tuscany 1.1 did only affect binding.sca and not
> binding.ws.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
