POJO和Java Beans的区别

POJO vs Java Beans

POJO classes

POJO stands for Plain Old Java Object. It is an ordinary Java object, not bound by any special restriction other than those forced by the Java Language Specification and not requiring any classpath. POJOs are used for increasing the readability and re-usability of a program. POJOs have gained the most acceptance because they are easy to write and understand. They were introduced in EJB 3.0 by Sun microsystems.
A POJO should not:

1. Extend prespecified classes, Ex: public class GFG extends javax.servlet.http.HttpServlet (…) is not a POJO class.
2. Implement prespecified interfaces, Ex: public class Bar implements javax.ejb.EntityBean (…) is not a POJO class.
3. Contain prespecified annotations, Ex: @javax.persistence.Entity public class Baz … is not a POJO class.

Java Beans

Beans are special type of Pojos. There are some restrictions on POJO to be a bean

1. All JavaBeans are POJOs but not all POJOs are JavaBeans.
2. Serializable i.e. they should implement Serializable interface. Still, some POJOs who don’t implement Serializable interface are called POJOs because Serializable is a marker interface and therefore not of much burden.
3. Fields should be private. This is to provide the complete control on fields.
4. Fields should have getters or setters or both.
5. A no-arg constructor should be there in a bean
6. Fields are accessed only by constructor or getter setters.

摘抄自POJO vs Java Beans