3 Replies Latest reply on Sep 16, 2010 11:11 AM by Nicholas Wurster

    WSDL error - Need help to remove "import location"

    Brad Baker Newbie

      HI all,

      I need some help.  I am useing jboss-4.2.0.GA and have made a new web service with the

      @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) anotation.

       

      Everything deploys fine but when I hit it to get the WSDL, somthing is very wrong.  My WSDL looks like this:


      <definitions name="WSEndPointPortImplService" targetNamespace="http://webservice.notification./" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://WSEndPoint.subscribews.ws." xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://webservice.notification/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <import location="https://HOST:8443/WS/WSEndPointPortImpl?wsdl&resource=WSEndPoint_PortType47500.wsdl" namespace="http://WSEndPoint.subscribews.ws" />
      <service name="WSEndPointPortImplService">
      <port binding="ns1:PRISMNotificationWSEndPointBinding" name="WSEndPointPortImplPort">
        <soap:address location="https://HOST:8443/WS/WSEndPointPortImpl" />
      </port>
      </service>
      </definitions>

       

      Now I have hacked up the names to protect the guilty but my man question is, why:

      <import  location="https://HOST:8443/WS/WSEndPointPortImpl?wsdl&resource=WSEndPoint_PortType47500.wsdl"  namespace="http://WSEndPoint.subscribews.ws" />

       

      Why did JBoss do this in two parts?  Why the "Import location"?  When I have done:

      @SOAPBinding(style = SOAPBinding.Style.RPC, use =  SOAPBinding.Use.LITERAL)

      JBoss generated a WSDL that was all one peace.

       

      The reason I think this is an issues is when I point to the url and attempt to generate client classes I get an cannot parse WSDL error.  I have never gotten this error when I do  RPC/Litteral.

       

      Please let me know if I can tell JBoss to not break my WSDL into two parts!

       

      Thanks,

      Brad