You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2010/03/23 10:15:15 UTC
Re: [2.x] What information should be serialized with
EndpointReference/Endpoint and how to resolve them on the consumer side?
On Mon, Dec 7, 2009 at 9:54 PM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> I have been trying to find out what information should be serialized with an
> Endpoint or EndpointReference and how they can be resolved (or rebuilt) by
> the consuming component. The current code serializes an EP or EPR as
> composite/component/reference|service/binding. I have put together a wiki
> page at [1] to illustrate the use cases and explain how an EP/EPR should be
> exchanged. Let's use it to discuss and fix the issues we have run into.
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Serialization+Deserialization+of+Endpoints+and+EndpointReferences
>
> Thanks,
> ---
> Raymond Feng
> Apache Tuscany PMC Member: http://tuscany.apache.org
> Co-author of Tuscany In Action (A book on Tuscany SCA):
> http://tuscanyinaction.com/
>
>
>
What ever happened with this thread, are there any conclusions?
Currently the serialized endpoint includes the implementation element
which means that when its propagated to a remote runtime there are
errors if the remote runtime doesn't include the extension for that
implementation type (thats a common situation when using the SCAClient
to access a remote service). So if nothing else from this thread i'd
like to remove the implementation from the serialized endpoint.
...ant
Re: [2.x] What information should be serialized with
EndpointReference/Endpoint and how to resolve them on the consumer side?
Posted by ant elder <an...@apache.org>.
On Tue, Mar 23, 2010 at 5:50 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Tue, Mar 23, 2010 at 2:15 AM, ant elder <an...@gmail.com> wrote:
>> What ever happened with this thread, are there any conclusions?
>> Currently the serialized endpoint includes the implementation element
>> which means that when its propagated to a remote runtime there are
>> errors if the remote runtime doesn't include the extension for that
>> implementation type (thats a common situation when using the SCAClient
>> to access a remote service). So if nothing else from this thread i'd
>> like to remove the implementation from the serialized endpoint.
>>
>> ...ant
>>
>
> I have started a schema and some processor for this issue, but didn't
> have time to finalize them yet.
>
Ok, for the time being then in r927277 I've just set the
implementation to null when the endpoint is being serialized.
...ant
Re: [2.x] What information should be serialized with
EndpointReference/Endpoint and how to resolve them on the consumer side?
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Mar 23, 2010 at 2:15 AM, ant elder <an...@gmail.com> wrote:
> What ever happened with this thread, are there any conclusions?
> Currently the serialized endpoint includes the implementation element
> which means that when its propagated to a remote runtime there are
> errors if the remote runtime doesn't include the extension for that
> implementation type (thats a common situation when using the SCAClient
> to access a remote service). So if nothing else from this thread i'd
> like to remove the implementation from the serialized endpoint.
>
> ...ant
>
I have started a schema and some processor for this issue, but didn't
have time to finalize them yet.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/