Hiranya, Lets introduce an internal flag to the endpoint so that the builder and the serializer pair sets and checks respectively to make the generated name transparent from the users configuration.
To address the issue of having different, UUID's on different server start sessions, we could compute the endpoint name by looking at the parent sequence name, for example like "main_ep_1" and so forth. Thanks, Ruwan On Mon, Apr 26, 2010 at 4:52 PM, Hiranya Jayathilaka <hiranya...@gmail.com>wrote: > Devs, > > Currently Synapse generates names for anonymous endpoints. For an example > take the following sequence: > > <sequence name="foo"> > <send> > <endpoint> > <address uri="some address"/> > </endpoint> > </send> > </sequence> > > Synapse will generate a UUID and set that as the name of the endpoint. This > is required since all endpoints must have names in clustered deployments. > However generating names causes the serialization to be different from the > original input XML. As a result we currently have a bunch of test failures > in the trunk. Any idea how to resolve this problem? > > Thanks > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
