RE: Difference between SOAP 1.1 vs 1.2 SOAPAction Support in AXIS 1.1

[Volkmann, Mark]

As far as I know, Axis hasn't been modified to support the new treatment of SOAPAction yet.

However, I think I understand how it's different in SOAP 1.2.

 

In SOAP 1.1 you'd have these HTTP headers.

 

Content-Type: text/xml

SOAPAction: "whatever"

 

In SOAP 1.2 you'd have just this HTTP header.

 

Content-Type: application/soap+xml; action=""

 

For those in the know, please correct me if I'm wrong.

-----Original Message-----
From: Tony Opatha [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 1:29 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Difference between SOAP 1.1 vs 1.2 SOAPAction Support in AXIS 1.1

Hi,

 

In SOAP 1.1 SOAPAction: is a HTTP Header that corresponds with

soapbind:operation soapAction="...".

 

How is the functionality of SOAPAction Header element

different in SOAP 1.2?

 

Does AXIS support both SOAP 1.1 and SOAP 1.2 and if it

does then what are the guidelines to use SOAPAction

w.r.t. Doc/Lit such that same WSDL spec could be used

for both SOAP 1.1 and SOAP 1.2?

 

Much appreciated your response.

 

Thanks

 

 

 

---

Do you Yahoo!?
Exclusive Video Premiere - Britney Spears



------------------------------------------------------------------------------------------
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other
than the recipient.

------------------------------------------------------------------------------------------