[ 
https://issues.apache.org/jira/browse/TUSCANY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516854
 ] 

Jean-Sebastien Delfino commented on TUSCANY-1497:
-------------------------------------------------

I suggest that the service references should implement externalizable and 
serialize by default into a human readable form.

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.

It should be possible to pass a service reference to a remote service in the 
middle of other business data (a pretty common use case IMO). This will require 
some specific support from the various Tuscany databindings.

Another use case is: Get a service reference, store it into some persistent 
storage, stop the runtime, restart it the next day or next year, read the 
service reference back and use it to invoke some services, possibly within the 
scope of the same long running conversation if the service reference was 
conversational.


> Add full support for service references (which can be passed accross binding 
> protocols)
> ---------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1497
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1497
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>            Reporter: Raymond Feng
>
> The Java spec defines CallableReference and ServiceReference. At this moment, 
> we only have limited support for local cases (keeping pointers to java 
> objects). We need to support the marshaling/unmarshaling of service 
> references accross binding protocols.

-- 
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]

Reply via email to