[
https://issues.apache.org/jira/browse/CXF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-5517.
------------------------------
Resolution: Fixed
Fix Version/s: 2.7.10
2.6.13
3.0.0-milestone2
I kept the Void.class comparison although it's probably unusual to get the
return type of Void.class.
The patch will perform comparison consistently against Void.TYPE (which is
equivalent to void.class) and Void.class.
> Incorrect check for VOID type
> -----------------------------
>
> Key: CXF-5517
> URL: https://issues.apache.org/jira/browse/CXF-5517
> Project: CXF
> Issue Type: Bug
> Reporter: Valentin Mayamsin
> Assignee: Aki Yoshida
> Labels: void
> Fix For: 3.0.0-milestone2, 2.6.13, 2.7.10
>
>
> There are multiple occurrences in CXF code base for both server and client
> side which incorrectly deals with VOID return type. For example:
> method.getReturnType() == Void.class
> This fails in case of primitive VOID:
> method.getReturnType() => void.class
> The correct way of checking for VOID is:
> method.getReturnType().equals(Void.TYPE)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
