Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-1.5
-
None
Description
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.