[
https://jira.jboss.org/jira/browse/JBWS-2205?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBWS-2205:
---------------------------------------
This is because of different StAX implementations being used in AS 5 and AS 4.2.
My analysis is the following: Metro seems to rely on the default encoding to be used when
creating messages. However sjsxp does not emit the encoding attribute when it is not
explicity set. Woodstox instead emits UTF-8 in such cases.
The AS5 uses Woodstox, that's why the xml declaration contains the encoding.
As a matter of fact setting on AS5
-Djavax.xml.stream.XMLInputFactory=com.sun.xml.stream.ZephyrParserFactory
-Djavax.xml.stream.XMLOutputFactory=com.sun.xml.stream.ZephyrWriterFactory
-Djavax.xml.stream.XMLEventFactory=com.sun.xml.stream.events.ZephyrEventFactory
cause the AS42 behavior (no encoding).
The same way, setting on AS42
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
-Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory
-Djavax.xml.stream.XMLEventFactory=com.ctc.wstx.stax.WstxEventFactory
you get the encoding in the xml declaration.
XML Declaration contains encoding in AS 5.x but not in AS 4.2.x
---------------------------------------------------------------
Key: JBWS-2205
URL:
https://jira.jboss.org/jira/browse/JBWS-2205
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-metro
Reporter: Heiko Braun
Assignee: Alessio Soldano
Fix For: jbossws-metro-3.0.4
Needs to be investigated how target contains are able to manipulate that behavior.
It's very likely that it's either a XML library feature (see woodstox or xerces
features) or an implementation detail that changed within a particular library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira