You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2007/09/13 10:35:33 UTC
[jira] Updated: (TUSCANY-1634) Review the propagation of
callable/service references over various bindings
[ https://issues.apache.org/jira/browse/TUSCANY-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino updated TUSCANY-1634:
--------------------------------------------
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Moving to SCA-Next as these JIRAs are not likely to be fixed by 1.0.
> Review the propagation of callable/service references over various bindings
> ---------------------------------------------------------------------------
>
> Key: TUSCANY-1634
> URL: https://issues.apache.org/jira/browse/TUSCANY-1634
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.0
> Reporter: Raymond Feng
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
>
> It should also have the ability to serialize to/from a URI and to/from a WS-addressing service endpoint reference.
> Bindings should transport service references in an appropriate binding specific format (possible leveraging the service reference's builtin serialization capabilities), for example:
> - Web Service binding -> serialize to a WS-addressing service endpoint reference, the target Web Service (possibly non SCA) should be able to use that EPR to call the SCA client back
> - JMS binding -> properties of the JMS message
> - EJB binding -> a valid reference to an EJB session bean? not sure about this one
> etc.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org