[jira] [Resolved] (CAMEL-14156) JmsBinding assumes endpoint can't be null, but it can

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-14156.
---------------------------------
    Resolution: Fixed

> JmsBinding assumes endpoint can't be null, but it can
> -----------------------------------------------------
>
>                 Key: CAMEL-14156
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14156
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-activemq, camel-jms
>    Affects Versions: 2.24.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 2.24.3, 3.0.0, 2.25.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> CAMEL-13750 introduces a change checking the {{endpoint}} in {{JmsBinding}}:
> {code}
> if (headerName.equals("JMSCorrelationID") && !endpoint.isUseMessageIDAsCorrelationID()) {
> {code}
> As {{endpoint}} can be null (for instance if you just do {{new JmsBinding()}}), this change is wrong as it can throw {{NullPointerException}}.
> I'm fixing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)