38

i am sure this must have been asked before in different ways - as isEmptyOrNull is so common yet people implement it differently. but i have below curious query in terms of best available approach which is good for memory and performance both.

1) Below does not account for all spaces like in case of empty XML tag

return inputString==null || inputString.length()==0;

2) Below one takes care but trim can eat some performance + memory

return inputString==null || inputString.trim().length()==0;

3) Combining one and two can save some performance + memory (As Chris suggested in comments)

return inputString==null || inputString.trim().length()==0 || inputString.trim().length()==0;

4) Converted to pattern matcher (invoked only when string is non zero length)

private static final Pattern p = Pattern.compile("\\s+");

return inputString==null || inputString.length()==0 || p.matcher(inputString).matches();

5) Using libraries like - Apache Commons (StringUtils.isBlank/isEmpty) or Spring (StringUtils.isEmpty) or Guava (Strings.isNullOrEmpty) or any other option?

prash
  • 896
  • 1
  • 11
  • 18
  • inputString!=null && inputString.isEmpty(); more refined inputString!=null && inputString.trim().isEmpty(); – StackFlowed Sep 14 '15 at 14:22
  • You can also use Apache String utils [isEmpty()](http://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringUtils.html#isEmpty(java.lang.CharSequence)) this does the null check as well as space checks. – StackFlowed Sep 14 '15 at 14:24
  • `isEmpty` is "new" in java 6 and implementations that are older or want to stay java 5 compatible will have to use length check. – zapl Sep 14 '15 at 14:37
  • 2
    If you do `return inputString==null || inputString.length()==0 || inputString.trim().length()==0;` (combining 1 and 2) then trim is only invoked on non-zero-length string. You might add 3 to it too., – Christian Fries Sep 14 '15 at 15:24
  • @ChristianFries Yes, I agree - same approach can be used for both trim() and pattern matcher. But let me ask it this way - trim() or matcher() which one is costlier? – prash Sep 14 '15 at 15:51
  • 1
    Guava has Strings.isNullOrEmpty() which i am using the most at the moment! – prash Oct 25 '16 at 17:28
  • Possible duplicate of [Check whether a string is not null and not empty](https://stackoverflow.com/questions/3598770/check-whether-a-string-is-not-null-and-not-empty) – Durgpal Singh Mar 26 '19 at 06:41

14 Answers14

41

Useful method from Apache Commons:

 org.apache.commons.lang.StringUtils.isBlank(String str)

https://commons.apache.org/proper/commons-lang/javadocs/api-2.6/org/apache/commons/lang/StringUtils.html#isBlank(java.lang.String)

puczo
  • 687
  • 4
  • 9
25

To detect if a string is null or empty, you can use the following without including any external dependencies on your project and still keeping your code simple/clean:

if(myString==null || myString.isEmpty()){
    //do something
}

or if blank spaces need to be detected as well:

if(myString==null || myString.trim().isEmpty()){
    //do something
}

you could easily wrap these into utility methods to be more concise since these are very common checks to make:

public final class StringUtils{

    private StringUtils() { }   

    public static bool isNullOrEmpty(string s){
        if(s==null || s.isEmpty()){
            return true;
        }
        return false;
    }

    public static bool isNullOrWhiteSpace(string s){
        if(s==null || s.trim().isEmpty()){
            return true;
        }
        return false;
    }
}

and then call these methods via:

if(StringUtils.isNullOrEmpty(myString)){...}

and

if(StringUtils.isNullOrWhiteSpace(myString)){...}

GregH
  • 5,125
  • 8
  • 55
  • 109
  • 1
    updated thanks. I inevitably make that mistake every time and then compile it, see the error, and realize ive made this mistake for the 9 billionth time :) – GregH Sep 14 '15 at 14:37
  • 1
    @zapl or statement in java is short-circuit. It will break if myString is null – James Wierzba Sep 14 '15 at 14:37
  • @JamesWierzba answer was `if (s.isEmpty||s==null)` which does short circuit with a NPE in case of null :) removed comment to avoid confusion. – zapl Sep 14 '15 at 14:59
  • And it doesnt take care of blank spaces :) – prash Jan 05 '18 at 05:35
  • The question only mentioned null or empty. If blank spaces need to be detected as well, then this can easily be changed to `if(myString==null || myString.trim().isEmpty()){...}` – GregH Mar 07 '18 at 14:43
  • 1
    String now has a .isBlank() method – user2303325 Apr 11 '19 at 18:45
15

Just to show java 8's stance to remove null values.

String s = Optional.ofNullable(myString).orElse("");
if (s.trim().isEmpty()) {
    ...
}

Makes sense if you can use Optional<String>.

Joop Eggen
  • 107,315
  • 7
  • 83
  • 138
  • Thanks Joop, I think this one is also a clean solution - It will not work for multi-space blank strings like " ". – prash Sep 14 '15 at 15:54
  • @prash: added a trim for good order, but apache commons is unbeatable. ;) – Joop Eggen Sep 14 '15 at 16:12
  • 3
    I have to say I think that the use of Optional is infecting the Java community like a bad disease. I have never before seen a feature that takes so much extra typing to achieve was is so simple yet adopted by so many sheeple at a time when competitive languages are going for more terse solutions. It must make non Java developers laugh at us. I haven't even mentioned the extra CPU and memory consumption when OptionalS are instantiated returned by methods that get called millions of times a second - but it's all running in the cloud so CPU and memory are almost free right? – Volksman Feb 02 '19 at 21:01
  • @Volksman I agree that 1. some other languages have better (designed) constructs, 2. Optional is a late addition, an artifact with an unripe API. But it is 1. better than null, 2. allows some nice operations à la map. – Joop Eggen Feb 04 '19 at 08:22
  • 1
    @JoopEggen I've been using polymorphic "Null" classes/objects since C++ days to store items in template/generic collections that "represent" null but I've recently been working in large scale systems that already have performance issues (CPU + Memory) processing thousands of txns/second. If we change working code that returns null by wrapping each return value in an Optional we'll be allocating thousands more objects on the heap every second, making a struggling system do more work for no benefit (IMHO) and a lot of pain or increased infrastructure costs to cope. Conceptually awesome though! – Volksman Feb 05 '19 at 09:11
  • @Volksman 100% true; also waves of small refactorings is productive (though one should refactor during development to keeep the code fine). Performance might surprise, but is indeed not optimal. – Joop Eggen Feb 05 '19 at 10:59
8

This one from Google Guava could check out "null and empty String" in the same time.

Strings.isNullOrEmpty("Your string.");

Add a dependency with Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>20.0</version>
</dependency>

with Gradle

dependencies {
  compile 'com.google.guava:guava:20.0'
}
mavis.chen
  • 91
  • 1
  • 3
4

Apache Commons Lang has StringUtils.isEmpty(String str) method which returns true if argument is empty or null

Ahmed Ashour
  • 5,179
  • 10
  • 35
  • 56
Evgeniy Dorofeev
  • 133,369
  • 30
  • 199
  • 275
4

Haven't seen any fully-native solutions, so here's one:

return str == null || str.chars().allMatch(Character::isWhitespace);

Basically, use the native Character.isWhitespace() function. From there, you can achieve different levels of optimization, depending on how much it matters (I can assure you that in 99.99999% of use cases, no further optimization is necessary):

return str == null || str.length() == 0 || str.chars().allMatch(Character::isWhitespace);

Or, to be really optimal (but hecka ugly):

int len;
if (str == null || (len = str.length()) == 0) return true;
for (int i = 0; i < len; i++) {
  if (!Character.isWhitespace(str.charAt(i))) return false;
}
return true;

One thing I like to do:

Optional<String> notBlank(String s) {
  return s == null || s.chars().allMatch(Character::isWhitepace))
    ? Optional.empty()
    : Optional.of(s);
}

...

notBlank(myStr).orElse("some default")
gzak
  • 3,908
  • 6
  • 33
  • 56
3

springframework library Check whether the given String is empty.

f(StringUtils.isEmpty(str)) {
    //.... String is blank or null
}
gifpif
  • 4,507
  • 4
  • 31
  • 45
  • 1
    As of Spring 5.3 `isEmpty` is deprecated. Instead, it's recommended to use following alternatives: `hasLength(String), hasText(String) or ObjectUtils.isEmpty(Object)` – Mihkel Selgal Mar 23 '21 at 11:00
2
Optional.ofNullable(label)
.map(String::trim)
.map(string -> !label.isEmpty)
.orElse(false)

OR

TextUtils.isNotBlank(label);

the last solution will check if not null and trimm the str at the same time

haneenCo
  • 169
  • 2
  • 7
1

Simply and clearly:

if (str == null || str.trim().length() == 0) {
    // str is empty
}
Community
  • 1
  • 1
simhumileco
  • 31,877
  • 16
  • 137
  • 115
1

In most of the cases, StringUtils.isBlank(str) from apache commons library would solve it. But if there is case, where input string being checked has null value within quotes, it fails to check such cases.

Take an example where I have an input object which was converted into string using String.valueOf(obj) API. In case obj reference is null, String.valueOf returns "null" instead of null.

When you attempt to use, StringUtils.isBlank("null"), API fails miserably, you may have to check for such use cases as well to make sure your validation is proper.

1

With the openJDK 11 you can use the internal validation to check if the String is null or just white spaces

import jdk.internal.joptsimple.internal.Strings;
...

String targetString;
if (Strings.isNullOrEmpty(tragetString)) {}
sachyy
  • 532
  • 4
  • 8
0

You can make use of Optional and Apache commons Stringutils library

Optional.ofNullable(StringUtils.noEmpty(string1)).orElse(string2);

here it will check if the string1 is not null and not empty else it will return string2

Deepak Pandey
  • 618
  • 7
  • 19
0

If you have to test more than one string in the same validation, you can do something like this:

import java.util.Optional;
import java.util.function.Predicate;
import java.util.stream.Stream;

public class StringHelper {

  public static Boolean hasBlank(String ... strings) {

    Predicate<String> isBlank = s -> s == null || s.trim().isEmpty();

    return Optional
      .ofNullable(strings)
      .map(Stream::of)
      .map(stream -> stream.anyMatch(isBlank))
      .orElse(false);
  }

}

So, you can use this like StringHelper.hasBlank("Hello", null, "", " ") or StringHelper.hasBlank("Hello") in a generic form.

rsa
  • 329
  • 2
  • 5
0

We can make use of below

Optional.ofNullable(result).filter(res -> StringUtils.isNotEmpty(res))
            .ifPresent( s-> val.set(s));
naveen
  • 21
  • 3