You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2009/07/15 15:31:15 UTC

[jira] Assigned: (TUSCANY-3140) Implementation.jee: The interface bound to the Runtimewire is not loaded with the class loader from implementation

     [ https://issues.apache.org/jira/browse/TUSCANY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws reassigned TUSCANY-3140:
-----------------------------------

    Assignee: Simon Laws

> Implementation.jee: The interface bound to the Runtimewire is not loaded with the class loader from implementation
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3140
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3140
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Misc Implementation Extensions
>    Affects Versions: Java-SCA-1.5
>            Reporter: Anbu Ponniah
>            Assignee: Simon Laws
>
> In external EAR scenario, the class loader used to resolve interface contracts on references is different from the run time class loader used to create the reference proxies. This causes "argument type mismatch" errors in data binding layer when custom data types are used as arguments in the referred service.
> Example scenario:
> An JavaEE application with a EJB session bean using a reference to an SCA service (via reference injection). The SCA service operation receives a Jaxb generated class as its input argument.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.