Talk:Plain old Java object

My opinion is that any general restriction or requirement other than those forced by the Java Language Specification on the java objects to be used in a program makes those objects not POJOs and those programming environments not strictly POJO compliant. In the case of annotations, requiring the existence of certain annotations is a restriction much like requiring the existence of certain methods. In addition, it also rules out the use of older versions of the JVM, including 1.4, which is still widely used in enterprise environments.

I guess we can debate the meaning of 'restriction'. At the very least, however, we should make it clear that the restriction placed by annotations is different from that placed by interfaces and base classes. While it may be (to quote you) 'much like requiring existence of certain methods', it is not the same.

The crucial difference is that annotations place no runtime dependencies: if they did, annotated POJOs would be no more lightweight than implementing marker interfaces.

Please redo my change and/or update it to your liking to emphasise this distinction.

Kennardconsulting 01:50, 21 August 2007 (UTC)[reply]

AfD discussion

Wikipedia:Articles for deletion/Plain Old Java Object (aeropagitica) (talk) 22:50, 21 April 2006 (UTC)[reply]

Please denote vernacular usage

This nomencalture is not part of a standard or specification. Please denote in the body of the article that such nomenclature should not be used in general and certainly not used in technical tests. (Common guys, you are going to crash planes with this stuff.)

Notability missing

Where is notability demonstrated for this subject?-- Mumia-w-18 20:21, 1 November 2007 (UTC)[reply]