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=3&rev2=4 If it were easier to get up and running, Jini would be a great solutions for most current users of SOA (we'll just ignore the fact that Jini predates current ideas of XML-based SOA). The archetypal SOA looks like this: - {{attachment:http://people.apache.org/~gtrasuk/ArchetypalSOA.png|Standard SOA with User interface talking to business process, invoking services through ESB|width=800}} + {{http://people.apache.org/~gtrasuk/ArchetypalSOA.png|Standard SOA with User interface talking to business process, invoking services through ESB|width=800}} 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.
