On Mon, May 7, 2012 at 6:03 PM, Afkham Azeez <az...@wso2.com> wrote: > > > On Mon, May 7, 2012 at 5:11 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote: > >> >> >> On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez <az...@wso2.com> wrote: >> >>> Folks., >>> Any feedback on this? Does this make sense? >>> >> >> I don't think so. We have a very clear separation between named >> sequences/endpoints and anonymous sequences/endpoints. Anonymous objects >> are local to a particular proxy service or an API and they are not visible >> to other services. Sort of like a private method. Named objects on the >> other hand are visible to everybody, can be shared/reused extensively and >> do show up in the Synape global namespace. Both have specific, well-defined >> use cases and I don't see a strong use case for having named sequences >> inside a proxy or an API. >> > > What about the service chaining scenario? We unnecessarily have to define > sequences in the global space even though those will be needed only by one > particular proxy service. Take a look at the example at > http://blog.afkham.org/2012/05/wso2-esb-service-chaining.html. I had to > define personInfoSeq & creditSeq at the global level even though I needed > them only within the proxy service. Is there a way to achieve the same > thing while keeping everything local (without following the old state > property based case handling)? >
In other words, is there a way to set the "receive" attribute of the send mediator to an anonymous (local to proxy service) sequence?
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
