Re: SOAPAction alternatives

Currently, many implementations will dispatch based on the child element
of the Body, so long as there is only one child element and that element
is unique amongst possible receptors.
 

-----Original Message-----
From: Fraser Goffin [mailto:[email protected]] 
Sent: Wednesday, November 06, 2002 2:57 AM
To: [email protected]
Subject: [SOAP] SOAPAction alternatives

Sorry to bring up an 'old chesnut' subject once again, but ..., my
organisation is moving ahead with the implementation of web services
which
are accessible over a number of transport protocols, and we feel the
need
for a protocol indpendant mechanism for identifying the requested
service
and operation which ultimately will be used to identifying the internal
target implementation. The vast majority of message exchanges use SOAP
in
document/literal form.

We already support ebXML MS and thus the SOAP Header elements which
convey
this intent, but, not all of our calling clients use ebXML and neither
do we
necessarilly want to force them to do so.

If there's a unilateral groan of 'oh not again' I would be happy to be
re-directed to threads which have previously discussed this one :-)

Cheers

Fraser.


_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other
DevelopMentor lists at http://discuss.develop.com.

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.