[JBoss JIRA] Created: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
5:04 a.m.
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
1 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=comments#action_12371357 ]
Mark Little commented on JBESB-783:
-----------------------------------
If this is purely a JBR issue, then we should close this one.
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
5:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ 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
4:17 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Tom Fennelly updated JBESB-783:
-------------------------------
Assignee: Tom Fennelly (was: Mark Little)
This is an issue for us. I'll take it. Thanks.
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: Tom Fennelly
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
4:17 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Work on JBESB-783 started by Tom Fennelly.
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: Tom Fennelly
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
4:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=comments#action_12375601 ]
Tom Fennelly commented on JBESB-783:
------------------------------------
Please vote JBREM-653
(http://jira.jboss.com/jira/secure/ViewVoters!addVote.jspa?key=JBREM-653). I through I
was doing something wrong when setting the content-type on the response - was still coming
back as text/html.
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: Tom Fennelly
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
4:27 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Tom Fennelly updated JBESB-783:
-------------------------------
Fix Version/s: 4.2.1
Affects Version/s: 4.2
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
Affects Versions: 4.2
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Tom Fennelly
Fix For: 4.2.1
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
7:04 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=comments#action_12375641 ]
Tom Fennelly commented on JBESB-783:
------------------------------------
I submitted a patch for JBREM-653.
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
Affects Versions: 4.2
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Tom Fennelly
Fix For: 4.2.1
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
9:56 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Tom Fennelly closed JBESB-783.
------------------------------
Resolution: Done
We are setting the content type, but as Bernard points out, JBossRemoting is ignoring it.
I patched this bug locally and verified that, if fixed, we'll be fine.
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
Affects Versions: 4.2
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Tom Fennelly
Fix For: 4.2.1
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
11:10 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Tom Fennelly reopened JBESB-783:
--------------------------------
Mark would like this left open for now, so as to catch it in the release notes. Can move
to next release then etc until resolved
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
Affects Versions: 4.2
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Tom Fennelly
Fix For: 4.2.1
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
12:17 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway
[ http://jira.jboss.com/jira/browse/JBESB-783?page=all ]
Mark Little closed JBESB-783.
-----------------------------
Resolution: Done
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
Affects Versions: 4.2
Environment: JBossESB Trunk
Reporter: Bernard Tison
Assigned To: Tom Fennelly
Fix For: 4.2.1
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
6788
days inactive
6821
days old
10 comments
3 participants
participants (3)
-
Bernard Tison (JIRA) -
Mark Little (JIRA)
-
Tom Fennelly (JIRA)