Talk:Plain old Java object/Archives/2015

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)

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


 * 1) Extend prespecified classes.
 * 2) Implement prespecified interfaces.
 * 3) 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)