[
https://issues.jboss.org/browse/JBWS-3339?page=com.atlassian.jira.plugin....
]
Kyle Lape updated JBWS-3339:
----------------------------
Labels: character_encoding webservices wsdl xsd (was: )
Description:
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:
{noformat}http://localhost:8080/testService/Service?wsdl&resource=external.xsd{noformat}
The file on the server starts like this:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema ...>
...
</xsd:schema>
{code}
But when it's served to a client, it starts like this:
{code:xml}
<xsd:schema ...>
...
</xsd:schema>
{code}
This affects the WSDL and any resources referenced by the WSDL.
was:
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.
Preamble is omitted when supplying external XSDs
------------------------------------------------
Key: JBWS-3339
URL:
https://issues.jboss.org/browse/JBWS-3339
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Kyle Lape
Labels: character_encoding, webservices, wsdl, xsd
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:
{noformat}http://localhost:8080/testService/Service?wsdl&resource=external.xsd{noformat}
The file on the server starts like this:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema ...>
...
</xsd:schema>
{code}
But when it's served to a client, it starts like this:
{code:xml}
<xsd:schema ...>
...
</xsd:schema>
{code}
This affects the WSDL and any resources referenced by the WSDL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira