[
https://issues.apache.org/jira/browse/CXF-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domagoj Cosic updated CXF-7880:
-------------------------------
Description:
In version 3.2.5 a classifier check was introduced in the if clause, in line
471 as of version 3.2.6:
{{classifier.equals(a.getClassifier())}}
but without null pointer protection, causing an NPE if classifier is null.
classifier may be null as the present check in line 476 (just 5 lines below)
demonstrates. The above clause could be rewritten as e.g.:
{{Objects.equals(classifier, a.getClassifier())}}
was:
In version 3.2.5 a classifier check was introduced in the if clause, in line
471 as of version 3.2.6:
{{classifier.equals(a.getClassifier())}}
but without null pointer protection, causing an NPE if classifier is null.
classifier may be null as the present check in line 476 (just 5 lines below)
demonstrates. It would easily solve the problem if you could rewrite the above
clause as e.g.:
{{Objects.equals(classifier, a.getClassifier())}}
> NullPointerException in org.apache.cxf.maven_plugin.Java2WSMojo
> ---------------------------------------------------------------
>
> Key: CXF-7880
> URL: https://issues.apache.org/jira/browse/CXF-7880
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 3.2.5, 3.2.6
> Reporter: Domagoj Cosic
> Priority: Major
>
> In version 3.2.5 a classifier check was introduced in the if clause, in line
> 471 as of version 3.2.6:
> {{classifier.equals(a.getClassifier())}}
> but without null pointer protection, causing an NPE if classifier is null.
> classifier may be null as the present check in line 476 (just 5 lines below)
> demonstrates. The above clause could be rewritten as e.g.:
> {{Objects.equals(classifier, a.getClassifier())}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
