Theoretically one could implement an SOA on top of services built using a different distributed technology (e.g., sockets, RMI or Corba), but that negates many of the architectural advantages that WS bring to the table. And, of course, WS are being implemented using other transports (Axis also has SMTP and JMS bindings), so the "W" in WS doesn't quite fit any more. Or, even more radically, one could drop SOAP altogether and transport something else, like JSON.
Originally posted by Timothy Sam: From my point of view... WS is one of those technologies involved to create SO Architecture.
Will it be possible to create a true SOA without using WS.If I write and implement my services using some non XML based service approach ; like corba , RMI , then will this architecture be termed as true SOA ?
The reason I am asking this is , SOA's one of the main objectives is discovery of services and consumption of it by various other service consumers (possibly non compatible).If this is the case then non xml protocols are directly ruled out.Only XML based protocols can be used for service invocation.(Considering that every client can successfully make use of XML )
As WS is the only widely standard for registering , finding and invocation of services , then its the only way by which a true SOA could be implemented.
Joined: Mar 22, 2005
SOA is an architectural concept. It can be implemented using a variety of technologies. Right now, SOAP is just about the only contender, since it's the only one that has the full infrastructure in place, as you point out. But nothing prevents you from implementing an SOA using different technologies (whether that would be a useful thing to do is an entirely different matter).
Joined: Nov 29, 2005
So I can put it like this , In todays date ,WS is the only way to achieve a true SO Architecture.
Originally posted by Rahul Bhattacharjee: (Considering that every client can successfully make use of XML)
Just because the client can discover the "syntax" of the XML document doesn't mean it can discover its "semantics" - which is ultimately what it needs to interpret the data correctly. You can only consume data from an arbitrary service if you are already familiar with the documents it offers (e.g. a domain standardized XML application). So once you are constrained by a pre-defined document that pre-defined document could be offered in a non-XML format.
Joined: Nov 29, 2005
Just bringing my post up , in case Mark Hansen has something to add to it.