Talk:Plain old Java object

	; Archives (Index) ;
	2013; 2014; 2015;
	This page is archived by ClueBot III.

Java Start‑class Low‑importance

	This article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaWikipedia:WikiProject JavaTemplate:WikiProject JavaJava
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

Special Object

The second sentence adds little to explanation of POJO. Merely saying that is it not a special object while not explaining what a special object or what it lacks that doesn't make it special doesn't clarify much to the reader:

"The name is used to emphasize that the object in question is an ordinary Java Object, not a special object, and in particular not an Enterprise JavaBean (especially before EJB 3)"

—Preceding unsigned comment added by 207.171.180.101 (talk • contribs)

Also you could call Special Objects "SPEJO", instead of SoJO, where the oh seems to come from nowhere, but whatever; this just crossed my mind and probably nobody uses SPEJO anyways.

Pupitetris (talk) 19:51, 15 July 2015 (UTC)[reply]

JavaBeans are not POJO. "Contextual variations" chapter misleading?

I have objections as to JavaBeans being listed as a "variation" of a POJO object. The definition in the first section says The term "POJO" is mainly used to denote a Java object which does not follow any of the major Java object models, conventions, or frameworks. By that definition, a JavaBean is not a POJO object (or a variation of it), since it introduces coding convention. I suggest the entire chapter is removed as it only causes confusion. — Preceding unsigned comment added by Nilzor (talk • contribs) 10:29, 15 May 2013 (UTC)[reply]

Transparently adding services

The title is not clear. What does it mean: "the services that are adding transparently", "the transparent process of adding services", or something else?

Definition

The Definition section outlines 3 things a POJO should not do:

Extend prespecified classes.
Implement prespecified interfaces.
Contain prespecified annotations.

What is the source for these requirements? Also, in what sense is "prespecified" being used? What makes an annotation prespecified as such - does it mean a requirement imposed by an external framework?

jon (talk) 20:57, 20 December 2015 (UTC)[reply]