Java Data Objects - Revision history

JJMC89 bot III: Moving :Category:Object-relational mapping to :Category:Object–relational mapping per Wikipedia:Categories for discussion/Speedy

2023-10-30T06:49:07Z

Moving Category:Object-relational mapping to Category:Object–relational mapping per Wikipedia:Categories for discussion/Speedy

← Previous revision		Revision as of 06:49, 30 October 2023
Line 99:		Line 99:

	{{Authority control}}		{{Authority control}}
	[[Category:~~Object-relational~~ mapping]]		[[Category:Object–relational mapping]]
	[[Category:Java enterprise platform\|Data Objects]]		[[Category:Java enterprise platform\|Data Objects]]
	[[Category:Java specification requests\|Data Objects]]		[[Category:Java specification requests\|Data Objects]]

InternetArchiveBot: Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.3

2023-03-03T17:21:14Z

Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.3

← Previous revision		Revision as of 17:21, 3 March 2023
Line 75:		Line 75:
	}}		}}
	* {{cite book		* {{cite book
	\| first = David		\|first = David
	\| last = Ezzio		\|last = Ezzio
	\| date = June 6, 2003		\|date = June 6, 2003
	\| title = Using and Understanding Java Data Objects		\|title = Using and Understanding Java Data Objects
	\| publisher = [[Apress]]		\|publisher = [[Apress]]
	\| edition = 1st		\|edition = 1st
	\| pages = 456		\|pages = 456
	\| isbn = 1-59059-043-0		\|isbn = 1-59059-043-0
	\| url = http://www.apress.com/book/view/9781590590430		\|url = http://www.apress.com/book/view/9781590590430
			\|access-date = February 8, 2010
			\|archive-date = December 23, 2010
			\|archive-url = https://web.archive.org/web/20101223171047/http://apress.com/book/view/9781590590430
			\|url-status = dead
	}}		}}
	{{refend}}		{{refend}}

HotMess: fixing Javadoc:SE usage

2022-11-13T02:08:41Z

fixing Javadoc:SE usage

← Previous revision		Revision as of 02:08, 13 November 2022
Line 21:		Line 21:
	* Standardized ORM mapping descriptors (for ORM-based JDO implementations)		* Standardized ORM mapping descriptors (for ORM-based JDO implementations)
	* JDOQL Enhancements (Single String Form; more String, Map & Math methods support mandated)		* JDOQL Enhancements (Single String Form; more String, Map & Math methods support mandated)
	* Get e.g. a {{Javadoc:SE\|java/sql\|Connection}} from <code>javax.jdo.PersistenceManager</code>		* Get e.g. a {{Javadoc:SE\|java/sql\|Connection\|module=java.sql}} from <code>javax.jdo.PersistenceManager</code>
	* More: Named Queries (pm.newNamedQuery), FetchPlan, Sequence, Delete by Query, multiple User Objects on PM		* More: Named Queries (pm.newNamedQuery), FetchPlan, Sequence, Delete by Query, multiple User Objects on PM

VulcanSphere: Adding short description: "Specification of Java object persistence" (Shortdesc helper)

2022-04-29T01:52:09Z

Adding short description: "Specification of Java object persistence" (Shortdesc helper)

← Previous revision		Revision as of 01:52, 29 April 2022
Line 1:		Line 1:
			{{Short description\|Specification of Java object persistence}}
	{{No footnotes\|date=June 2010}}		{{No footnotes\|date=June 2010}}
	'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.		'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.

Lenux2.0: minor edit.

2021-01-19T07:40:09Z

minor edit.

← Previous revision		Revision as of 07:40, 19 January 2021
Line 39:		Line 39:
	* [[DataNucleus]]		* [[DataNucleus]]
	* [[ObjectDB]]		* [[ObjectDB]]
	* [[ActiveJPA]]		* ActiveJPA

	==Bibliography==		==Bibliography==

Persistability: other reference implementations to list

2020-08-04T12:22:55Z

other reference implementations to list

← Previous revision		Revision as of 12:22, 4 August 2020
Line 29:		Line 29:
	* JDO 2.1 : JPOX 1.2		* JDO 2.1 : JPOX 1.2
	* JDO 2.2 : [[DataNucleus]] AccessPlatform 1.0.1		* JDO 2.2 : [[DataNucleus]] AccessPlatform 1.0.1
	* JDO 3.0 : DataNucleus AccessPlatform 2.1.0		* JDO 3.0 : [[DataNucleus]] AccessPlatform 2.1.0
			* JDO 3.1 : [[DataNucleus]] AccessPlatform 3.2.0
			* JDO 3.2 : [[DataNucleus]] AccessPlatform 5.2.0

	== See also ==		== See also ==

DannyS712: Removing from Category:Java platform - remove diffusing parent category; already in subcategory - using Cat-a-lot

2019-03-05T03:23:55Z

Removing from Category:Java platform - remove diffusing parent category; already in subcategory - using Cat-a-lot

← Previous revision		Revision as of 03:23, 5 March 2019
Line 93:		Line 93:
	{{Authority control}}		{{Authority control}}
	[[Category:Object-relational mapping]]		[[Category:Object-relational mapping]]
	[[Category:Java platform\|Data Objects]]
	[[Category:Java enterprise platform\|Data Objects]]		[[Category:Java enterprise platform\|Data Objects]]
	[[Category:Java specification requests\|Data Objects]]		[[Category:Java specification requests\|Data Objects]]

84.226.133.74 at 11:51, 3 July 2017

2017-07-03T11:51:16Z

← Previous revision		Revision as of 11:51, 3 July 2017
Line 1:		Line 1:
	{{No footnotes\|date=June 2010}}		{{No footnotes\|date=June 2010}}
	'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain ~~Old~~ Java ~~Object~~\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.		'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.

	Object persistence is defined in the external [[XML]] metafiles, which may have vendor-specific extensions. JDO vendors provide developers with ''enhancers'', which modify compiled Java class files so they can be transparently persisted. (Note that byte-code enhancement is not mandated by the JDO specification, although it is the commonly used mechanism for implementing the JDO specification's requirements.) Currently, JDO vendors offer several options for persistence, e.g. to [[Relational database\|RDBMS]], to [[Object database\|OODB]], or to [[Computer file\|files]].		Object persistence is defined in the external [[XML]] metafiles, which may have vendor-specific extensions. JDO vendors provide developers with ''enhancers'', which modify compiled Java class files so they can be transparently persisted. (Note that byte-code enhancement is not mandated by the JDO specification, although it is the commonly used mechanism for implementing the JDO specification's requirements.) Currently, JDO vendors offer several options for persistence, e.g. to [[Relational database\|RDBMS]], to [[Object database\|OODB]], or to [[Computer file\|files]].

96.89.90.57: /* JDO vs. EJB3 vs. JPA */

2017-01-13T17:45:47Z

JDO vs. EJB3 vs. JPA

← Previous revision		Revision as of 17:45, 13 January 2017
Line 9:		Line 9:

	== JDO vs. EJB3 vs. JPA ==		== JDO vs. EJB3 vs. JPA ==
	[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards ~~conflict~~ between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.		[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflicts between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.

	In the end, persistence has been "broken out" of "EJB3 Core", and a new standard formed, the [[Java Persistence API]] (JPA). JPA uses the <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> will '''not''' require an EJB container, and thus will work within a Java SE environment as well, as JDO always has. JPA, however, is an [[object-relational mapping]] (ORM) standard, while JDO is both an object-relational mapping standard and a transparent object persistence standard. JDO, from an API point of view, is agnostic to the technology of the underlying datastore, whereas JPA is targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).		In the end, persistence has been "broken out" of "EJB3 Core", and a new standard formed, the [[Java Persistence API]] (JPA). JPA uses the <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> will '''not''' require an EJB container, and thus will work within a Java SE environment as well, as JDO always has. JPA, however, is an [[object-relational mapping]] (ORM) standard, while JDO is both an object-relational mapping standard and a transparent object persistence standard. JDO, from an API point of view, is agnostic to the technology of the underlying datastore, whereas JPA is targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).

77.56.53.183: /* JDO vs. EJB3 vs. JPA */

2016-06-10T09:00:20Z

JDO vs. EJB3 vs. JPA

← Previous revision		Revision as of 09:00, 10 June 2016
Line 9:		Line 9:

	== JDO vs. EJB3 vs. JPA ==		== JDO vs. EJB3 vs. JPA ==
	[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with Entity ~~Beans~~. There have been standards conflict between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.		[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflict between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.

	In the end, persistence has been "broken out" of "EJB3 Core", and a new standard formed, the [[Java Persistence API]] (JPA). JPA uses the <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> will '''not''' require an EJB container, and thus will work within a Java SE environment as well, as JDO always has. JPA, however, is an [[object-relational mapping]] (ORM) standard, while JDO is both an object-relational mapping standard and a transparent object persistence standard. JDO, from an API point of view, is agnostic to the technology of the underlying datastore, whereas JPA is targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).		In the end, persistence has been "broken out" of "EJB3 Core", and a new standard formed, the [[Java Persistence API]] (JPA). JPA uses the <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> will '''not''' require an EJB container, and thus will work within a Java SE environment as well, as JDO always has. JPA, however, is an [[object-relational mapping]] (ORM) standard, while JDO is both an object-relational mapping standard and a transparent object persistence standard. JDO, from an API point of view, is agnostic to the technology of the underlying datastore, whereas JPA is targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).

← Previous revision		Revision as of 01:52, 29 April 2022
Line 1:		Line 1:
			{{Short description\|Specification of Java object persistence}}
	{{No footnotes\|date=June 2010}}		{{No footnotes\|date=June 2010}}
	'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.		'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.

← Previous revision		Revision as of 11:51, 3 July 2017
Line 1:		Line 1:
	{{No footnotes\|date=June 2010}}		{{No footnotes\|date=June 2010}}
	'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain ~~Old~~ Java ~~Object~~\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.		'''Java Data Objects''' ('''JDO''') is a specification of [[Java platform\|Java]] [[object (computer science)\|object]] [[Persistence (computer science)\|persistence]]. One of its features is a transparency of the persistence services to the [[domain model]]. JDO persistent objects are ordinary [[Java (programming language)\|Java programming language]] [[class (computer science)\|classes]] ([[Plain old Java object\|POJOs]]); there is no requirement for them to implement certain [[interface (Java)\|interfaces]] or extend from special classes. JDO 1.0 was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=12 JSR 12]. JDO 2.0 was developed under [http://www.jcp.org/en/jsr/detail?id=243 JSR 243] and was released on May 10, 2006. JDO 2.1 was completed in Feb 2008, developed by the [http://db.apache.org/jdo/ Apache JDO] project. JDO 2.2 was released in October 2008. JDO 3.0 was released in April 2010.

	Object persistence is defined in the external [[XML]] metafiles, which may have vendor-specific extensions. JDO vendors provide developers with ''enhancers'', which modify compiled Java class files so they can be transparently persisted. (Note that byte-code enhancement is not mandated by the JDO specification, although it is the commonly used mechanism for implementing the JDO specification's requirements.) Currently, JDO vendors offer several options for persistence, e.g. to [[Relational database\|RDBMS]], to [[Object database\|OODB]], or to [[Computer file\|files]].		Object persistence is defined in the external [[XML]] metafiles, which may have vendor-specific extensions. JDO vendors provide developers with ''enhancers'', which modify compiled Java class files so they can be transparently persisted. (Note that byte-code enhancement is not mandated by the JDO specification, although it is the commonly used mechanism for implementing the JDO specification's requirements.) Currently, JDO vendors offer several options for persistence, e.g. to [[Relational database\|RDBMS]], to [[Object database\|OODB]], or to [[Computer file\|files]].