-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
-
Documented as Resolved Issue
The content-type mime header is properly set to application/fastinfoset in request messages, but is still set to application/soap+xml or text/xml for response.
This is fixed in the jbossws-native-4.0 mentioned in the jira https://issues.jboss.org/browse/JBWS-3192.
We need to port the changes to the eap maintenance branch https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-3.1.2
- blocks
-
JBPAPP-4552 Release and upgrade JBossWS Native
- Closed
- incorporates
-
JBWS-3192 content-type header is not properly set for FastInfoset response messages
- Closed