WSDL published via SOAPProxy or SOAPProcessor has no XML declaration

Solution Unverified - Updated -

Issue

  • The WSDL which is published via SOAPProxy or SOAPProcessor on the JBoss ESB has no XML declaration like following:
<definitions name='HelloWorldWSService' targetNamespace='http://simple_invoke/helloworld'
    xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
    xmlns:tns='http://simple_invoke/helloworld' xmlns:xsd='http://www.w3.org/2001/XMLSchema'
    xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype">
  ...
  • The original WSDL from a Web service which is proxied by SOAPProxy or SOAPProcessor, however, has the XML declaration at the top of the document:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions name='HelloWorldWSService' targetNamespace='http://simple_invoke/helloworld'
    xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
    xmlns:tns='http://simple_invoke/helloworld' xmlns:xsd='http://www.w3.org/2001/XMLSchema'
    xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype">
  ...
  • Doesn't this make the WSDL invalid?

Environment

  • JBoss Enterprise SOA Platform
    • 5.x SOAPProxy
    • 5.3 SOAPProcessor

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In