Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).
Description
Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).
This issue is really a bug as far as JBossESB is concerned. JBossESB supports a number of transports/connectors via JBossRemoting. A number of other features also rely on JBossRemoting e.g. SOAP/HTTP. Therefore, in the case of webservices support, not being able to set the Content-Type on http responses effectively means we can't guarantee interoperability since many clients will refuse to process responses that don't have indicate an appropriate Content-Type.
Ron Sigal [03/Oct/07 08:32 PM]
Comment by Tom Fennelly:
This issue is really a bug as far as JBossESB is concerned. JBossESB supports a number of transports/connectors via JBossRemoting. A number of other features also rely on JBossRemoting e.g. SOAP/HTTP. Therefore, in the case of webservices support, not being able to set the Content-Type on http responses effectively means we can't guarantee interoperability since many clients will refuse to process responses that don't have indicate an appropriate Content-Type.
Bug
Closed
Major
allow user to set content-type for http responses (CLONE of JBREM-653)
This issue is really a bug as far as JBossESB is concerned. JBossESB supports a number of transports/connectors via JBossRemoting. A number of other features also rely on JBossRemoting e.g. SOAP/HTTP. Therefore, in the case of webservices support, not being able to set the Content-Type on http responses effectively means we can't guarantee interoperability since many clients will refuse to process responses that don't have indicate an appropriate Content-Type.