On Mon, Dec 7, 2009 at 1: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 >
>From the wiki page, it seems that we are currently serializing more info then needed (The current code serializes the endpoint as a composite/component/service/binding XML). I can see couple options to optimize this : - optimize the cloned composite/endpoint/service/binding by removing reference to unnecessary information - create a EP/EPR schema which would hold only the necessary information that needs to be submitted remotely IMO, the second options seems to allow for better flexibility/optimizations and if people agree I could try improving the code to perform this. Thoughts ? -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
