Gervas Douglas wrote: > /<<Abstract: Object-oriented programming languages and techniques > provide a powerful means for designing and building applications. These > techniques do not always translate well into a service oriented > paradigm. Service orientation demands a different set of design > guidelines and requirements than an object-oriented application. > Understanding how an object-oriented design can negatively impact a > service-oriented design is key to building services that support an > agile enterprise. This article examines where the two designs impact > each other as well as methods for addressing the incompatibilities > between the two while still leveraging the power of both. /
This article illustrates how broken "detached marshalling" is as a concept. It very uniquely illustrates how powerful Java's mobile code model really is, and why you should be using that as your integration tool, and not this amazing menagerie of nonsense, called .Net. Wow, I had no idea people were actually trying to do such (humm, I don't guess I have a PC word to put here) things as a way to simplify their development processes. This is why Java object orientation works well for SOA interfaces. Because we don't have to jump through such hoops to get between JVMs. And yes, you can place a Java service as a client-service bridge in the network to do odd marshalling conversions if needed for these kinds of nightmares. Gregg Wonderly
