@Callback should not be required on forward Java interface if component
ref/service intf definition fully defines forward/callback interface pair
-------------------------------------------------------------------------------------------------------------------------------------------------
Key: TUSCANY-2658
URL: https://issues.apache.org/jira/browse/TUSCANY-2658
Project: Tuscany
Issue Type: Bug
Components: Java SCA Java Implementation Extension
Reporter: Scott Kurz
If we have a component reference/service interface definition which contains a
forward/callback interface pair, then our runtime should not also require the
@Callback to be present on the forward Java interface.
E.g. if we have:
<component name="CallBackBasicClient">
<implementation.java ... />
<reference name="aCallBackService"
target="CallBackBasicService">
<interface.java
interface="org.apache.tuscany.sca.test.CallBackBasicService"
callbackInterface="org.apache.tuscany.sca.test.CallBackBasicCallBack"/>
</reference>
...
<component name="CallBackBasicService">
<implementation.java .../>
<service name="CallBackBasicService">
<interface.java
interface="org.apache.tuscany.sca.test.CallBackBasicService"
callbackInterface="org.apache.tuscany.sca.test.CallBackBasicCallBack"/>
</service>
</component>
then we shouldn't require the CallBackBasicService class to carry the
annotation: @Callback(CallBackBasicCallBack.class)
In modifying the itest/callback-basic test I saw we had this problem (will
attach this recreate patch).
Issue was discussed here
http://www.mail-archive.com/[email protected]/msg03087.html
and the motivating use case was the desire to avoid having to add @Callback to
a wsimport-generated Java interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
