Implementations of the org.osoa.sca Java API should not be in core
------------------------------------------------------------------
Key: TUSCANY-1864
URL: https://issues.apache.org/jira/browse/TUSCANY-1864
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0
Environment: All
Reporter: Simon Nash
Fix For: Java-SCA-Next
There are a number of implementation classes for Java-specific APIs that are
currently in core/context:
CallableReferenceImpl
ComponentContextImpl
ConversationImpl
RequestContextImpl
ServiceReferenceImpl
Having these classes in core causes problems when trying to fully implement
their spec semantics, because some of these semantics need
Java-specific code. The example that I am struggling with at the moment is
ServiceReferenceImpl.setCallback() which can take either
an instance of a Java implementation class or a service reference. If the
former is passed, ServiceReferenceImpl should check to make
sure it implements the callback interface and is Serializable (see section
1.6.7.5 of the Java Annotations and APIs spec). This is not
possible without using Java-specific code, but I don't want to make the core
module dependent on the implementation-java-runtime module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
