I’m not sure what you mean by XML
messaging architecture, but the main difference between SOAP and an integration
architecture is that SOAP has nothing to say about either the semantics of the
message or about the actual headers to use in the envelope. To create an
integration architecture you need to do both in addition to creating
well-defined interfaces described by WSDL. Typically, message semantics are
managed by having canonical forms of the message with mappings to and from them
(these could be in XSLT if your messages are XML). Message headers need to
enable envelope based routing, message integrity, correlation of requests and
replies, and security. Finally, if your transport does not offer guaranteed
delivery, you need to add headers to ensure once only delivery (as well as
writing the code to do it).
John Schlesinger
SysCore Solutions
-----Original Message-----
From: Satish
[mailto:satish@verchaska.com]
Sent: Thursday, May 30, 2002 2:20
AM
To: xml-dev@lists.xml.org
Subject: [xml-dev] xml messaging
architecture and SOAP
I am particularly new working in
xml. I would like to know the difference between xml messaging architecture and
SOAP technology.
Which one suits which kind of
solution, advantages and disadvantages, requirements, etc. The aim of using xml
in our organisation is related to EAI, webservices in particular, and
also for enhancing the current sun's pet store like architecture, having
refelections technology which we use for soultion development. So information
about any xml related utilities for the latter purpose also welcome.
Any help would be highly
appreciated.
