Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.4.2
-
None
-
None
-
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: C:\Java\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: C:\Java\apache-maven-3.0.3\bin\.. Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
-
Unknown
Description
While debugging our server, I saw in org.apache.cxf.endpoint.ClientImpl.invoke(BindingOperationInfo, Object[], Exchange):
Map<String, Object> resp = new HashMap<String, Object>(); resp.clear();
That's silly and a noop. Attaching patch to remove and do:
Map<String, Object> resp = new HashMap<String, Object>();
If you want an empty map to avoid wasting space for a rarely used feature, perhaps use:
Map<String, Object> resp = new HashMap<String, Object>(0);
or:
Map<String, Object> resp = new HashMap<String, Object>(1);