Suppose you have
boolean active;
Accessors method would be
public boolean isActive(){return this.active;}
public void setActive(boolean active){this.active = active;}
See Also
More Related Contents:
- Coding Conventions – Naming Enums
- Naming convention for getters/setters in Java
- Valid JavaBeans names for boolean getter methods
- What is a JavaBean exactly?
- Difference between DTO, VO, POJO, JavaBeans?
- Is it ok if I omit curly braces in Java? [closed]
- .toArray(new MyClass[0]) or .toArray(new MyClass[myList.size()])?
- Is it bad to explicitly compare against boolean constants e.g. if (b == false) in Java?
- for loop optimization
- Generic type parameter naming convention for Java (with multiple chars)?
- Variable naming conventions in Java
- JavaBean wrapping with JavaFX Properties
- Are there best practices for (Java) package organization? [closed]
- What is java pojo class, java bean, normal class? [duplicate]
- Should a “static final Logger” be declared in UPPER-CASE?
- Should methods in a Java interface be declared with or without a public access modifier?
- Java Naming Convention with Acronyms [closed]
- Conveniently map between enum and int / String
- Programmatically configure LogBack appender
- Any reason to clean up unused imports in Java, other than reducing clutter?
- Use of the String(String) constructor in Java [duplicate]
- JavaFX Beans Binding suddenly stops working
- Using underscores in Java variables and method names [closed]
- ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/mail/MessagingException
- Gracefully avoiding NullPointerException in Java
- find out the differences between two java beans for version tracking
- Java data transfer object naming convention?
- Oracle Java code conventions
- how to generically compare entire java beans?
- Java Interface Usage Guidelines — Are getters and setters in an interface bad?