Talk:Plain old Java object/Archives/2015
 | This is an archive of past discussions about Plain old Java object. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
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.
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?