Axis2 Binding's OperationClient needs to be reset to support repeated invocation
--------------------------------------------------------------------------------

                 Key: TUSCANY-662
                 URL: http://issues.apache.org/jira/browse/TUSCANY-662
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Axis Binding
    Affects Versions: Java-M2
         Environment: Revision: 433239   
            Reporter: Scott Kurz


When I invoke my service w/ WS binding (Axis2) a second time I get the 
following exception stack trace:

java.lang.reflect.InvocationTargetException
        at 
org.apache.tuscany.binding.axis2.Axis2TargetInvoker.invokeTarget(Axis2TargetInvoker.java:138)
        at 
org.apache.tuscany.binding.axis2.Axis2TargetInvoker.invoke(Axis2TargetInvoker.java:145)
        at 
org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44)
        at 
org.apache.tuscany.core.wire.jdk.AbstractJDKOutboundInvocationHandler.invoke(AbstractJDKOutboundInvocationHandler.java:75)
        at 
org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke(JDKOutboundInvocationHandler.java:83)
        ... 32 more
Caused by: org.apache.axis2.AxisFault: Invalid message addition , operation 
context completed
        at 
org.apache.axis2.description.OutInAxisOperation.addMessageContext(OutInAxisOperation.java:64)
        at 
org.apache.axis2.context.OperationContext.addMessageContext(OperationContext.java:89)
        at 
org.apache.axis2.description.AxisOperation.registerOperationContext(AxisOperation.java:369)
        at 
org.apache.axis2.description.OutInAxisOperationClient.addMessageContext(OutInAxisOperation.java:158)
        at 
org.apache.tuscany.binding.axis2.Axis2TargetInvoker.invokeTarget(Axis2TargetInvoker.java:99)

In looking at the source for method addMessageContext in class 
org.apache.axis2.description.OutInAxisOperation it appears that the operation 
context needs to be reset or cleared somehow so that both the in and out values 
are not set during subsequent invocations after the first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to