[
http://jira.jboss.com/jira/browse/JBESB-783?page=comments#action_12373091 ]
Bernard Tison commented on JBESB-783:
-------------------------------------
Technically this is indeed a JBR issue, but it affects ESB. Some Web Service clients (e.g.
JBossWS clients) will throw an exception when the response content type is not text/xml ot
application/soap+xml.
If JBREM-653 is fixed (I voted for it), it will allow to explicitely set the response
content type in the JBossRemoting Gateway to the desired value.
Response content type when invoking web service through JBoss
Remoting gateway
------------------------------------------------------------------------------
Key: JBESB-783
URL:
http://jira.jboss.com/jira/browse/JBESB-783
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Mark Little
When invoking a webservice through the JBoss Remoting Gateway (like in the
webservice_producer quickstart), the content type of the response is set by JBoss Remoting
to text/html. This can cause issues for certain clients who expect text/xml or
application/soap+xml as content type.
Currently JBoss remoting does not allow to explicitely set the response content type.
There is a JIRA for this (JBREM-653), but it is still open.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira