You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org> on 2009/03/20 00:55:50 UTC
[jira] Created: (QPID-1762) java client blows up when it gets a
mime type it doesn't recognize
java client blows up when it gets a mime type it doesn't recognize
------------------------------------------------------------------
Key: QPID-1762
URL: https://issues.apache.org/jira/browse/QPID-1762
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.5
Reporter: Rafael H. Schloming
Assignee: Rafael H. Schloming
Fix For: 0.5
The java client throws an exception when it gets a mime type it doesn't recognize. This makes interop with non java clients difficult since they sometimes set the mime type to a value for which there is no registered decoder. The java client should really default to decoding as a bytes message in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-1762) java client blows up when it gets a
mime type it doesn't recognize
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming resolved QPID-1762.
---------------------------------------
Resolution: Fixed
> java client blows up when it gets a mime type it doesn't recognize
> ------------------------------------------------------------------
>
> Key: QPID-1762
> URL: https://issues.apache.org/jira/browse/QPID-1762
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Rafael H. Schloming
> Assignee: Rafael H. Schloming
> Fix For: 0.5
>
>
> The java client throws an exception when it gets a mime type it doesn't recognize. This makes interop with non java clients difficult since they sometimes set the mime type to a value for which there is no registered decoder. The java client should really default to decoding as a bytes message in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org