The XML preamble is omitted when serving external WSDL resources. This can cause problem when specifying a non-default character set using the XML preamble.

For example, you access an external XSD:

http://localhost:8080/testService/Service?wsdl&resource=external.xsd

The file on the server starts like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema ...>
  ...
</xsd:schema>

But when it's served to a client, it starts like this:

<xsd:schema ...>
  ...
</xsd:schema>

This affects the WSDL and any resources referenced by the WSDL.

Looking at the code, this is what happens when a request for a WSDL resource is received:

• The WSDL resource is read in from the file system.
• It is then parsed into a DOM tree.
• JBossWS then replaces references to external resources with appropriate URLs that can be reached using "?wsdl" URLs.
• The DOM tree is then marshaled to XML text.

In this process, the XML preamble is lost.