You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2014/07/16 19:10:05 UTC

[jira] [Updated] (PROTON-631) Potential null pointer exception if 'x-opt-jms-type' annotation is present but has a null value.

     [ https://issues.apache.org/jira/browse/PROTON-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated PROTON-631:
----------------------------------

    Summary: Potential null pointer exception if 'x-opt-jms-type' annotation is present but has a null value.  (was: Potentiual null pointer exception is JMSType property is present but has a null value.)

> Potential null pointer exception if 'x-opt-jms-type' annotation is present but has a null value.
> ------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-631
>                 URL: https://issues.apache.org/jira/browse/PROTON-631
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.7
>            Reporter: Timothy Bish
>            Assignee: Robbie Gemmell
>             Fix For: 0.8
>
>         Attachments: patch.txt
>
>
> If a JMS mapping client sends a message with the "x-opt-jms-type" set but with a value of null the InboundTransformer will throw a NullPointerException since it tries to perform a toString() without first checking for null. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)