Why Using isXXX Naming for Boolean Fields in Java Is Discouraged: Guidelines and Examples

In Java development, the naming convention for Boolean fields often causes confusion; the article argues that using the isXXX pattern for both primitive boolean and wrapper Boolean types is not recommended.

According to Alibaba's Java Development Manual and the JavaBeans specification, primitive boolean properties should have getters prefixed with is and setters with set , while wrapper types must use getXXX() and setXXX() . The article provides several code examples:

private String isHot;
public String getIsHot() { return isHot; }

private boolean isHot;
public boolean isHot() { return isHot; }

private Boolean isHot;
public Boolean getHot() { return isHot; }

private boolean hot;
public boolean isHot() { return hot; }

private Boolean hot;
public Boolean getHot() { return hot; }

The article highlights that using isSuccess() for a Boolean wrapper can mislead RPC frameworks, which may interpret the property name as success instead of isSuccess , leading to serialization errors.

Key takeaways include:

Avoid naming Boolean fields with the is prefix to prevent RPC serialization issues.

For POJOs, prefer wrapper types ( Boolean , Integer , etc.) so that null values can indicate missing data, while using primitive types for local variables.

Follow the JavaBeans getter/setter conventions strictly to ensure compatibility with tools and frameworks.

By adhering to these guidelines, developers can write clearer, more reliable Java code and avoid subtle bugs in distributed systems.