I kind of agree with Kirit; the only thing I don't agree with is that a POJO can extend a class or implement an interface. But the most important thing is that doesn't comply with the Java Bean's rules, i.e. have getter/setter methods for each attribute.

Still, the POJO term is quite confusing when reading docs from different framework vendors, e.g. Hibernate, Apache Struts etc.