Indika, I see this as a good suggestion... so the routing information is kept in the registry and the next endpoint is looked up from the registry. So that it is going to be a set of equivalent EPR's in most of the part.
Extracting the endpoint address from the message is a special case to me and I don't think we should support that by default. There is a two step process which is explained in the first mail by Supun. Thanks, Ruwan On Fri, Jun 26, 2009 at 2:53 PM, indika kumara <[email protected]>wrote: > Supun > > Could you extend this to enable looking up EPR from a routing table > defined in the registry as an XML.? > > Thanks > Indika > > On Fri, Jun 26, 2009 at 11:00 AM, Supun Kamburugamuva<[email protected]> > wrote: > > Hi all, > > > > I got this idea and I thought of asking it from the community. > > > > I think it is better to have the flexibility to change an endpoint > address > > dynamically. At the moment we can achieve this with DefaultEndpoint or > using > > a send mediator without an Endpoint. In both these cases we can change > the > > address by using the header mediator to set the To. Or we can use the > > incoming To address without using a HeaderMediator. > > > > But if we want to change the address of a loadbalance or > failover endpoint > > dynamically, this won't work. So my idea is to allow the endpoints to use > an > > expression to pick the endpoint address. > > > > This may be valid or I might be missing something :). Your comments are > > welcome. > > > > Thanks, > > Supun.. > > -- > > Software Engineer, WSO2 Inc > > http://wso2.org > > http://supunk.blogspot.com > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
