[
https://issues.apache.org/jira/browse/TUSCANY-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627305#action_12627305
]
Simon Laws commented on TUSCANY-2501:
-------------------------------------
Conversation relating to this JIRA has been going on on the mail list here
(http://www.mail-archive.com/[email protected]/msg01953.html) and is seems
that this error is the know on effect of the specs implying that if you mix
annotated and unannotated references then the unannotated references are
ignored. The code changes relating to this JIRA cause an error to be raised if
the user tries to mix annotated and unannotated references.
> A couple places where InterfaceContract is not established on reference when
> it's not calculated by introspection
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2501
> URL: https://issues.apache.org/jira/browse/TUSCANY-2501
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Reporter: Scott Kurz
> Fix For: Java-SCA-Next
>
> Attachments: 2501.recreate.dont.commit.me.diff
>
>
> The vtests have a couple examples which result in component references being
> created without a corresponding InterfaceContract.
> This is not a problem with the current default binding impl (as these tests
> are currently passing), but a switch to using the WS binding, say, shows the
> issue.
> I'll attach a patch, too, but here are the issues:
> ------------------------------------------------------------------------------
> In vtest/java-api/apis/componentcontext:
> return componentContext.getService(DComponent.class,
> "dReference").getName();
> In vtest/java-api/annotations/reference
> public class AServiceImpl implements AService {
> ....
> public BService b4; // field injection (public, un-annotated)
> ------------------------------------------------------------------------------
> In both cases, the SCDL merely configures the ref target (and binding) but
> does not define the ref intf.
> I haven't given this area a great deal of thought, my guess is we want to
> extend our Java introspection capabilities, though I could see that for some
> impl
> types the better answer might be to require the SCDL to configure the intf in
> component SCDL.
> I didn't try the latter either, but wanted to just write up the issue for now.
> Thanks,
> Scott
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
