On Mon, Dec 7, 2009 at 9:54 PM, Raymond Feng <[email protected]> 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
