You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2011/07/30 18:26:10 UTC
[jira] [Created] (QPID-3380) Allow to get/set encoding type for JMS
messages
Allow to get/set encoding type for JMS messages
-----------------------------------------------
Key: QPID-3380
URL: https://issues.apache.org/jira/browse/QPID-3380
Project: Qpid
Issue Type: Improvement
Components: Java Client
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.14
The JMS API does not provide a way to get/set the content type.
Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3380) Allow to get/set encoding type for JMS
messages
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-3380:
-----------------------------------
Description:
The JMS API does not provide a way to get/set the content type.
Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
We could use "x-amqp.content-type" as the message property (key) to retrieve the content-type from the underlying message properties.
was:
The JMS API does not provide a way to get/set the content type.
Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
> Allow to get/set encoding type for JMS messages
> -----------------------------------------------
>
> Key: QPID-3380
> URL: https://issues.apache.org/jira/browse/QPID-3380
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: 0.14
>
>
> The JMS API does not provide a way to get/set the content type.
> Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
> The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
> Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
> However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
> We could use "x-amqp.content-type" as the message property (key) to retrieve the content-type from the underlying message properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Closed] (QPID-3380) Allow to get/set encoding type for JMS
messages
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu closed QPID-3380.
----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 0.15)
> Allow to get/set encoding type for JMS messages
> -----------------------------------------------
>
> Key: QPID-3380
> URL: https://issues.apache.org/jira/browse/QPID-3380
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
>
> The JMS API does not provide a way to get/set the content type.
> Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
> The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
> Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
> However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
> We could use "x-amqp.content-type" as the message property (key) to retrieve the content-type from the underlying message properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-3380) Allow to get/set encoding type for JMS
messages
Posted by "Rajith Attapattu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-3380:
-----------------------------------
Fix Version/s: (was: 0.14)
0.15
> Allow to get/set encoding type for JMS messages
> -----------------------------------------------
>
> Key: QPID-3380
> URL: https://issues.apache.org/jira/browse/QPID-3380
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: 0.15
>
>
> The JMS API does not provide a way to get/set the content type.
> Therefore it would be nice to allow a way to get/set the AMQP content type via the message properties.
> The JMS API (and the Qpid API) relies on the content-type for identifying map, text and eventually list messages.
> Therefore the user needs to be careful when using the above feature and we need to put a stern warning in our documentation about this.
> However when using bytes and text messages, this improvement allows a nice way for an application to provide specialized content-types like "text/xml" ..etc.
> We could use "x-amqp.content-type" as the message property (key) to retrieve the content-type from the underlying message properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org