Announcement

Collapse
No announcement yet.

Error defining a WS output channel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error defining a WS output channel

    Hi.

    I'm trying to define a SOAP output. I'm testing it again a .NET defined WSDL

    Affeter writing the WSDL URI, and pushing the "Get Method" button, an error box displays the messge "No Methods found, check the WSDL URI and try again". Of course, de WSDL is fine, and it's a WS running OK.

    In the log I ge the next output:

    Code:
    [SslListener0-1] org.mortbay.jetty.context.Mirth Server: /configuration: 
    java.lang.NullPointerException
    	at com.webreach.mirth.server.util.WebServiceReader.buildComplexTypes(WebServiceReader.java:215)
    	at com.webreach.mirth.server.util.WebServiceReader.buildComplexTypes(WebServiceReader.java:205)
    	at com.webreach.mirth.server.util.WebServiceReader.buildParams(WebServiceReader.java:194)
    	at com.webreach.mirth.server.util.WebServiceReader.getWSDefinition(WebServiceReader.java:177)
    	at com.webreach.mirth.server.servlets.ConfigurationServlet.doPost(ConfigurationServlet.java:81)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    	at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    	at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
    	at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
    	at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
    	at org.mortbay.http.HttpServer.service(HttpServer.java:909)
    	at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
    	at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
    	at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
    	at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
    	at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
    	at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
    I've tried with a WS defined by Mirth at another channel, and everything works fine. The WS I'm trying to connect to is located into another machine ¿Can be this the problem? ¿Or it's related to an incompatibilitity between jetty and .NET?

    Thanks for your time


  • #2
    Re: Error defining a WS output channel

    Can you email a link to the WSDL - we'll try to get a fix in 1.4

    Thanks!
    -Chris
    Chris Lang

    Comment


    • #3
      Re: Error defining a WS output channel

      I can't put the WSDL URI as it's internal.

      I think the problem is related to the xsd:any element defined in the WSDL.

      Code:
        <?xml version="1.0" encoding="utf-8" ?> 
       <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/Sistema/HL7" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/Sistema/HL7" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
       <wsdl:types>
       <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/Sistema/HL7">
       <s:element name="RecibirMensaje">
       <s:complexType>
       <s:sequence>
       <s:element minOccurs="0" maxOccurs="1" name="DocumentoXML">
       <s:complexType mixed="true">
       <s:sequence>
        <s:any /> 
        </s:sequence>
        </s:complexType>
        </s:element>
        </s:sequence>
        </s:complexType>
        </s:element>
        </s:schema>
        </wsdl:types>
       <wsdl:message name="RecibirMensajeSoapIn">
        <wsdl:part name="parameters" element="tns:RecibirMensaje" /> 
        </wsdl:message>
       <wsdl:portType name="HL7Soap">
       <wsdl:operation name="RecibirMensaje">
        <wsdl:input message="tns:RecibirMensajeSoapIn" /> 
        </wsdl:operation>
        </wsdl:portType>
       <wsdl:binding name="HL7Soap" type="tns:HL7Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
       <wsdl:operation name="RecibirMensaje">
        <soap:operation soapAction="http://tempuri.org/Sistema/HL7/RecibirMensaje" style="document" /> 
       <wsdl:input>
        <soap:body use="literal" /> 
        </wsdl:input>
        </wsdl:operation>
        </wsdl:binding>
       <wsdl:service name="HL7">
        <documentation xmlns="http://schemas.xmlsoap.org/wsdl/" /> 
       <wsdl:port name="HL7Soap" binding="tns:HL7Soap">
        <soap:address location="http://172.19.10.100/testingStage/ws/hl7/hl7.asmx" /> 
        </wsdl:port>
        </wsdl:service>
        </wsdl:definitions>

      Comment


      • #4
        Re: Error defining a WS output channel

        If you think it is a network/firewall issue try to read the WSDL from the .NET machine using a browser. If .NET can&#039;t get it, but your browser can then its a .NET/VisualStudio problem. If your browser can&#039;t see it then its a network or other config issue.
        Jon Bartels

        Zen is hiring!!!!
        http://consultzen.com/careers/
        Talented healthcare IT professionals wanted. Engineers to sales to management.
        Good benefits, great working environment, genuinely interesting work.

        Comment


        • #5
          Re: Error defining a WS output channel

          I can get the WS from my explorer, and from the WS consume both from my workstation and from Mirth&#039;s server.

          I&#039;m pretty sure than the problem is related to the "xsd:any" type.

          Comment


          • #6
            Re: Error defining a WS output channel

            Thanks for the WSDL - we&#039;ll run this through our SOAP test cases and hopefully get a fix in. The null-pointer-exception you get is an indicator that there is probably something we can fix.

            Thanks!
            -Chris
            Chris Lang

            Comment

            Working...
            X