You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Seumas Soltysik (JIRA)" <ji...@apache.org> on 2008/09/17 23:45:46 UTC
[jira] Created: (CXF-1805) Use of Content-Type in JMS Header not in
line with JMS specification
Use of Content-Type in JMS Header not in line with JMS specification
--------------------------------------------------------------------
Key: CXF-1805
URL: https://issues.apache.org/jira/browse/CXF-1805
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.1.2
Reporter: Seumas Soltysik
Priority: Blocker
It looks like the use of "Content-Type" as a JMS header property is illegal.
When using the JMS transport with Weblogic, I got the following error:
Caused by: java.io.IOException: weblogic.jms.common.MessageFormatException: Illegal property name, 'Content-Type'
at org.apache.cxf.transport.jms.JMSConduit$JMSOutputStream.doClose(JMSConduit.java:263)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
After doing some googling I found this: http://www.nabble.com/-jira--Created:-(SYNAPSE-424)-JMS-transport-uses-JMS-properties-in-a-way-that-violates-the-JMS-specifications-td18932701.html
Dan K also pointed out the following: The SOAP over JMS spec uses the header name: SOAPJMS_contentType
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1805) Use of Content-Type in JMS Header not
in line with JMS specification
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632192#action_12632192 ]
Ulhas Bhole commented on CXF-1805:
----------------------------------
Hi Seumas,
The problem is appearing due to copying of PROTOCOL_HEADERS on the JMS Message. I will change the things to use JMS_content_type and do the translations while adding/retrieving the Content-Type Header.
-- Ulhas Bhole
> Use of Content-Type in JMS Header not in line with JMS specification
> --------------------------------------------------------------------
>
> Key: CXF-1805
> URL: https://issues.apache.org/jira/browse/CXF-1805
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1.2
> Reporter: Seumas Soltysik
> Assignee: Ulhas Bhole
> Priority: Blocker
>
> It looks like the use of "Content-Type" as a JMS header property is illegal.
> When using the JMS transport with Weblogic, I got the following error:
> Caused by: java.io.IOException: weblogic.jms.common.MessageFormatException: Illegal property name, 'Content-Type'
> at org.apache.cxf.transport.jms.JMSConduit$JMSOutputStream.doClose(JMSConduit.java:263)
> at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
> After doing some googling I found this: http://www.nabble.com/-jira--Created:-(SYNAPSE-424)-JMS-transport-uses-JMS-properties-in-a-way-that-violates-the-JMS-specifications-td18932701.html
> Dan K also pointed out the following: The SOAP over JMS spec uses the header name: SOAPJMS_contentType
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1805) Use of Content-Type in JMS Header not
in line with JMS specification
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulhas Bhole reassigned CXF-1805:
--------------------------------
Assignee: Ulhas Bhole
> Use of Content-Type in JMS Header not in line with JMS specification
> --------------------------------------------------------------------
>
> Key: CXF-1805
> URL: https://issues.apache.org/jira/browse/CXF-1805
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1.2
> Reporter: Seumas Soltysik
> Assignee: Ulhas Bhole
> Priority: Blocker
>
> It looks like the use of "Content-Type" as a JMS header property is illegal.
> When using the JMS transport with Weblogic, I got the following error:
> Caused by: java.io.IOException: weblogic.jms.common.MessageFormatException: Illegal property name, 'Content-Type'
> at org.apache.cxf.transport.jms.JMSConduit$JMSOutputStream.doClose(JMSConduit.java:263)
> at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
> After doing some googling I found this: http://www.nabble.com/-jira--Created:-(SYNAPSE-424)-JMS-transport-uses-JMS-properties-in-a-way-that-violates-the-JMS-specifications-td18932701.html
> Dan K also pointed out the following: The SOAP over JMS spec uses the header name: SOAPJMS_contentType
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1805) Use of Content-Type in JMS Header not
in line with JMS specification
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulhas Bhole resolved CXF-1805.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2
2.1.3
2.0.9
Fixed the problem. It now uses SOAPJMS_contentType when putting or retrieving PROTOCOL_HEADER to/from JMSMessage.
> Use of Content-Type in JMS Header not in line with JMS specification
> --------------------------------------------------------------------
>
> Key: CXF-1805
> URL: https://issues.apache.org/jira/browse/CXF-1805
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1.2
> Reporter: Seumas Soltysik
> Assignee: Ulhas Bhole
> Priority: Blocker
> Fix For: 2.0.9, 2.1.3, 2.2
>
>
> It looks like the use of "Content-Type" as a JMS header property is illegal.
> When using the JMS transport with Weblogic, I got the following error:
> Caused by: java.io.IOException: weblogic.jms.common.MessageFormatException: Illegal property name, 'Content-Type'
> at org.apache.cxf.transport.jms.JMSConduit$JMSOutputStream.doClose(JMSConduit.java:263)
> at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
> After doing some googling I found this: http://www.nabble.com/-jira--Created:-(SYNAPSE-424)-JMS-transport-uses-JMS-properties-in-a-way-that-violates-the-JMS-specifications-td18932701.html
> Dan K also pointed out the following: The SOAP over JMS spec uses the header name: SOAPJMS_contentType
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.