Plain old Java object: Difference between revisions

Revision as of 20:03, 10 March 2021

Revision as of 05:05, 1 May 2021

Line 4:

</blockquote>

The term "POJO" initially denoted a Java object which does not follow any of the major Java object models, conventions, or frameworks; nowadays "POJO" may be used as an acronym for [[plain old JavaScript object]] as well, in which case the term denotes a [[JavaScript]] object of similar pedigree.<ref>{{cite web |url=http://ajaxian.com/archives/return-of-the-pojo-plain-ole-javascript |title=Return of the POJO: Plain ‘Ole'Ole JavaScript |last=Almaer |first=Dion |work=Ajaxian |date=2006-07-17 |access-date=2014-08-19 }}</ref>

The term continues the pattern of older terms for technologies that do not use fancy new features, such as [[plain old Ruby object]] (PORO) in [[Ruby (programming language)|Ruby]], [[plain old telephone service]] (POTS) in [[telephony]] and [[Plain Old Documentation]] (pod) in [[Perl]]. The equivalent to POJO on the [[.NET Framework]] is [[Plain old CLR object|plain Old CLR object]] (POCO).<ref>{{cite web |url=http://msdn.microsoft.com/en-us/library/cc681329.aspx |title=POCO Support |work=microsoft.com |access-date=2012-05-27 }}

Line 112:

{{Reflist|refs=

<ref name="RAD">{{cite book|title=Rational Application Developer V7.5 Programming Guide|first1=Ueli|last1=Wahli|first2=Miguel|last2=Vieira|first3=Ferreira Lopes|last3=Gomes|first4=Brian|last4=Hainey|first5=Ahmed|last5=Moharram|first6=JuanPablo|last6=Napoli|first7=Marco|last7=Rohr|first8=Henry|last8=Cui|first9=Patrick|last9=Gan|first10=Celso|last10=Gonzalez|first11=Pinar|last11=Ugurlu|first12=Lara|last12=Ziosi|date=29 June 2009|publisher=IBM Redbooks|isbn=978-0738432892 }}</ref>

}}