*
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes Why client must set BindingProvider.SOAPACTION_URI_PROPERTY? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "Why client must set BindingProvider.SOAPACTION_URI_PROPERTY?" Watch "Why client must set BindingProvider.SOAPACTION_URI_PROPERTY?" New topic
Author

Why client must set BindingProvider.SOAPACTION_URI_PROPERTY?

Himai Minh
Ranch Hand

Joined: Jul 29, 2012
Posts: 722
In JAX-WS 2.1 specification, it says "the client must also set BindingProvider.SOAPACTION_URI_PROPERTY."
In the example, the client sends a request like this:

In line 014, the <wsa:Action> has already specified "http://example.com/fabrikam/SubmitPO" , this action comes from the WSDL.
Probably the service has code like this:

But why the client must do this to set the soap action in the HTTP header like the following?

The receiver just needs to process the header blocks like <wsa:To> and <wsa:Action>. I don't understand why the SOAPACTION in the HTTP header must be set.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why client must set BindingProvider.SOAPACTION_URI_PROPERTY?
 
Similar Threads
JAXWS w/ WS Addressing
WS-Address working example
My Groovy Script Fails to Pick Up XML Element Value
WS-Addressing 2005/08 in JAX-WS
Using WS-RM with Axis2 1.5?