[OFBIZ-7310] Use UtilValidate.isEmpty() instead of length() <= 0

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Done
• Affects Version/s: Trunk
• Fix Version/s: 16.11.01
• Component/s: ALL COMPONENTS
• Assignee: Jacques Le Roux
• Reporter: Jacques Le Roux
• Created: 12/Jun/16 10:54
• Updated: 23/Dec/16 10:15
• Resolved: 12/Jun/16 10:59

Description

While reviewing Wai's patch for OFBIZ-7112 I noticed that he (re)used this pattern introduced earlier:

  (resource == null || resource.length() <= 0)

From Java spec. a String, Collection, Map or CharSequence can't have a negative length, so the pattern above can be reduced to

  (resource == null || resource.length() == 0)

which can be replaced using

  UtilValidate.isEmpty()

I checked, there are several other occurrences of this pattern (some very old, I guess most were routinely copied from an initial occurrence). I decided to replace all of them.

I did that already long ago for the

  (resource == null || resource.length() == 0)

pattern. It remains 4 of them. Three are justified (because of the dependency on base component or because using isEmpty() on Object is disputable for performance reasons). I'll took care of the remaining one right away!

Issue Links

• is related to: OFBIZ-4427 Runtime errors with UtilValidate.isEmpty(Object) and IsNotEmpty should be caught during compilation