You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2019/11/08 09:50:00 UTC
[jira] [Created] (CAMEL-14156) JmsBinding assumes endpoint can't be
null, but it can
Jean-Baptiste Onofré created CAMEL-14156:
--------------------------------------------
Summary: 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: Task
Components: camel-activemq, camel-jms
Affects Versions: 2.24.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 2.23.5, 2.24.3, 3.0.0, 2.25.0, 3.0.0.RC4
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)