Hi, I've just been looking at some IBM blurb about creating stateful web service implementations using something called WS-Addressing Stateful web services Is this an IBM proprietry mechanism or has it become a standard. Does anyone have any other links for this sort of thing? TIA Graham
WS-Addressing is not proprietary, as it has been submited by Microsoft, IBM and BEA, and I think it is now under OASIS's umbrella. I did not read the article (sorry) but I believe WS-Addressing is not about stateful Web services. Nevertheless, it sounds like IBM suggests to use WS-Resource and WS-Addressing in order to modelize stateful web servies. But something is puzzling me here. My understanding is that SOA requires stateless services. And web services claim to be SOA... Are SOA and stateful compatible ??
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Originally posted by Jean-Louis Marechaux: My understanding is that SOA requires stateless services. And web services claim to be SOA... Are SOA and stateful compatible ??
Although it is a recommended practice to make services as stateless as possible, I could imagine a service that persists state and requires clients to refer to a "session id" in their requests. Not sure about the "official" point of view on stateful services, though.