I believe a software system can have service-oriented characteristics, regardless of how it is used. One can point to a particular attribute of a software system and classify it as service- oriented. A software system design can be guided/constrained by SOA principles, and can thus be characterized as service-oriented.
This characterization can be technology agnostic. It doesn't matter if WS-* or JMS or ESB, et. al. have been used or not within the software system. It can still have service-oriented characteristics. I do agree that "SOA compliance" is highly suspect (and primarily a marketing device), since such a notion is highly dependent on the definition of SOA and to date there are no "compliance" test suites defined (as many have pointed out). -Rob --- In [email protected], Eric Newcomer <[EMAIL PROTECTED]> wrote: > > We at IONA would not claim "SOA compliance" since such a thing doesn't exist and probably can't or at least shouldn't. > > SOA is a style of design, or an approach to IT. It's not something > with which any particular product can be compliant since any number > of technologies can be (and have been) successfully used to > imlpement an SOA. That means it's how you use the product, not the > product or technology itself, that needs to be SOA compliant. > > Eric
