Announcement Announcement Module
No announcement yet.
BasicHttpBinding on Spring Webservices Client Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • BasicHttpBinding on Spring Webservices Client


    Please pardon my indulgence as this might get really lengthy, especially because I want to give enough information that way interested gurus can decipher the issue pronto.

    I am a building a super client that accesses a bunch of web services and one of them happens to be a dot net web services that uses BasicHttpBinding. All the other end points work without perfectly but for some reason I am not able to get the do net end point to behave in a civilize manner.

    As the error bellow will show, my soap message is generated correct and sent through the wire. When I copy the generated soap-env from my console and past it on soapUI it works fine. However, the same soap message comes back with a fault message saying: (There is no security on this web service...)
    HTML Code:
           <s:Envelope xmlns:s="">
                               <faultcode xmlns:a="">a:ActionNotSupported</faultcode>
                               <faultstring xml:lang="en-US">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g." Message, Transport, None).
    Again when I past the same generated soap message in SoapUI, it works well.
    Question, can someone please send me pointers on how to configure basicHttpBinding? I think that is all I need at the moment and should be able to get going if that can be provided to me.

    Thanks a million in advance for your time..... cheers!

  • #2

    Did you solve the problem?
    I've got the same and looking for solution.


    • #3
      I found solution by reading post:

      The problem was in soapAction name. WebService expected fully qualified name. My app was sending soapAction=MethodName.