[
https://issues.apache.org/jira/browse/TUSCANY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe resolved TUSCANY-1620.
-----------------------------------------
Resolution: Fixed
With Raymond's advice, the NotificationImplementationProvider now sets the
databinding in the interface contract, rather than relying on the deprecated
scdl databinding extension. See r570563.
This takes care of the subject of this issue and so it can be resolved.
> Exception running the binding-notification-producer sample
> ----------------------------------------------------------
>
> Key: TUSCANY-1620
> URL: https://issues.apache.org/jira/browse/TUSCANY-1620
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Data Binding Runtime, Java SCA Samples
> Affects Versions: Java-SCA-0.99, Java-SCA-1.0
> Environment: WIndows XP
> Reporter: Ignacio Silva-Lepe
> Assignee: Raymond Feng
> Fix For: Java-SCA-0.99, Java-SCA-1.0
>
>
> I am getting the following exception trying to run the binding-notification-
> producer sample and trying to send a message to a binding-notification-
> consumer. The NotificaitonReferenceBindingInvoker is expecting an
> OMElement that should be coming from the notification component via
> the corresponding databinding. But I don't see a databinding interceptor
> between the RuntimeSCABindingInvoker and the NotificationReference-
> BindingInvoker, the way you see it in the databinding-echo trace of
> TUSCANY-1582.
> Any ideas as to why the databinding interceptor is not being added to the
> invocation chain?
>
> java.lang.RuntimeException: payload not OMElement
> at
> org.apache.tuscany.sca.binding.notification.NotificationReferenceBind
> ingInvoker.getWriteableFromPayload(NotificationReferenceBindingInvoker.java:115)
>
> at
> org.apache.tuscany.sca.binding.notification.NotificationReferenceBind
> ingInvoker.invoke(NotificationReferenceBindingInvoker.java:81)
> at
> org.apache.tuscany.sca.implementation.notification.NotificationCompon
> entInvoker.invoke(NotificationComponentInvoker.java:81)
> at
> org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo
> ke(RuntimeSCABindingInvoker.java:48)
> at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke
> (JD
> KInvocationHandler.java:236)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD
> KInvocationHandler.java:93)
> at $Proxy8.trafficNotification(Unknown Source)
> at
> notification.producer.TrafficAdvisoryProducer.produceTrafficNotificat
> ion(TrafficAdvisoryProducer.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tuscany.sca.implementation.java.invocation.JavaImplementat
> ionInvoker.invoke(JavaImplementationInvoker.java:91)
> at
> org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo
> ke(RuntimeSCABindingInvoker.java:48)
> at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke
> (JD
> KInvocationHandler.java:236)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD
> KInvocationHandler.java:93)
> at $Proxy7.produceTrafficNotification(Unknown Source)
> at
> notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServe
> r.java:45)
--
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]
