• Post Reply Bookmark Topic Watch Topic
  • New Topic

Why client must set BindingProvider.SOAPACTION_URI_PROPERTY?

 
Himai Minh
Ranch Hand
Posts: 1400
8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Let's get him boys! We'll make him read this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!