[
https://issues.apache.org/jira/browse/TUSCANY-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Edwards updated TUSCANY-3026:
----------------------------------
Attachment: Tuscany_3026.patch
Patch file for fix:
> Promoted references involving different declared Interface types at different
> levels in the hierarchy fail
> ----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3026
> URL: https://issues.apache.org/jira/browse/TUSCANY-3026
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-2.0
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.0
>
> Attachments: Tuscany_3026.patch
>
>
> This JIRA is raised since Tuscany Java SCA fails the OASIS SCA Assembly
> testcase
> ASM_4007_TestCase.
> The failure is manifested by an exception at runtime when a Reference is
> invoked, where a null databinding is reported.
> The testcase involves 3 level of composites - Top level (A), middle tier (B)
> and bottom level (C). A has a component that hsa B as its implementation and
> B has a component with C as its implementation and C contains a single
> component with a Java POJO implementation. The Java POJO has a single
> reference, which is successively promoted to the top level and is wired to a
> target service at the top level, through a reference target on the component
> in A.
> The significant feature of the arrangement is that the reference is declared
> explicitly with a Java interface in C, but in B and in A the reference is
> explicitly declared with an equivalent WSDL interface (the WSDL is a direct
> translation of the Java).
> The failure occurs because of the WSDL interface on the Composite Reference
> in B - chaning this for a Java interface, or removing the explicit
> declaration from this place makes the error go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
