javax.xml.ws.WebServiceException: Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse

Mirth Project | Teru Morimura | 8 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    SOAP Listener response doesn't have correct namespace, it should be "http://components.mule.server.mirth.webreach.com" Here's the response I received: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:acceptMessageResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://DefaultNamespace"><acceptMessageReturn xsi:type="xsd:string">Message: c623c22f-a90c-463e-85c7-9b123532859a has been successfully received</acceptMessageReturn></ns1:acceptMessageResponse></soapenv:Body></soapenv:Envelope> Error message from Metro: javax.xml.ws.WebServiceException: Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse(ResponseBuilder.java:614) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:121) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy34.acceptMessage(Unknown Source)

    Mirth Project | 8 years ago | Teru Morimura
    javax.xml.ws.WebServiceException: Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse
  2. 0

    SOAP Listener response doesn't have correct namespace, it should be "http://components.mule.server.mirth.webreach.com" Here's the response I received: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:acceptMessageResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://DefaultNamespace"><acceptMessageReturn xsi:type="xsd:string">Message: c623c22f-a90c-463e-85c7-9b123532859a has been successfully received</acceptMessageReturn></ns1:acceptMessageResponse></soapenv:Body></soapenv:Envelope> Error message from Metro: javax.xml.ws.WebServiceException: Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse(ResponseBuilder.java:614) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:121) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy34.acceptMessage(Unknown Source)

    Mirth Project | 8 years ago | Teru Morimura
    javax.xml.ws.WebServiceException: Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse
  3. 0

    Jax-WS MTOM enabling issue

    Stack Overflow | 4 years ago | Timofei
    javax.xml.ws.WebServiceException: Missing Start Boundary, or boundary does not start on a new line
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JAXWS NetBeans 6.1 Jdk 1.6.0 tomcat 6.0.18 | Java.net

    java.net | 2 years ago
    javax.xml.ws.WebServiceException: Unsupported endpoint address:
  6. 0

    SOAP request returns EOFException in Web Logic

    Stack Overflow | 1 year ago | Rajesh Balan
    javax.xml.ws.WebServiceException: java.io.EOFException: Response contained no data

  1. JPMSoftwire 1 times, last 10 months ago
12 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. javax.xml.ws.WebServiceException

    Unexpected response element {http://DefaultNamespace}acceptMessageResponse expected: {http://components.mule.server.mirth.webreach.com}acceptMessageResponse

    at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse()
  2. JAX-WS RI Runtime Bundle
    SEIStub.invoke
    1. com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse(ResponseBuilder.java:614)
    2. com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:121)
    3. com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
    4. com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
    4 frames
  3. Unknown
    $Proxy34.acceptMessage
    1. $Proxy34.acceptMessage(Unknown Source)
    1 frame