+1. I think the problem is that people think contract is an interface. Developers using DI container such as Spring use interfaced-based design. However, that does not mean using Spring to build applications results in SOA.
The problem I think is the networking logic which is often associated with service are being written in with the business logic codes. H.Ozawa --- In [email protected], JP Morgenthal <[EMAIL PROTECTED]> wrote: > Interface-based design and design-by-contract are not > one-in-the-same, but as long as a majority of individuals > implementing SOA don't understand this delicate delineation, SOA > will suffer. Clearly, for many software engineers, they see a > service as a reusable component, while for many of us that have > been at this game awhile, we see a service as a more declarative > entity oriented strongly toward a business bent. >
