Dear Wiki user, You have subscribed to a wiki page or wiki category on "River Wiki" for change notification.
The "JavaBasedSOA" page has been changed by GregTrasuk: http://wiki.apache.org/river/JavaBasedSOA?action=diff&rev1=1&rev2=2 Looking at this from a Jini/River perspective, we can make a few observations: * By decoupling service location through the registrar, and allowing for dynamically downloaded proxies that implement whatever protocol the service wants, Jini makes most of the ESB functionality (a magic connectivity cloud) unnecessary. - * Standard SOA's concept of + * Standard SOA's concept of adapters could be seen as a variant of the Surrogate architecture. The big difference is that Surrogate assumes that the non-Java service is an active participant in the Jini network. To implement the SOA adapter pattern, we need to be able to add a surrogate without the non-Java service initiating it (not a big change to the Surrogate architecture).
