Content repository API for Java - Revision history

imported>Brentjz: /* Available implementations */

2025-06-24T11:06:36Z

Available implementations

← Previous revision		Revision as of 11:06, 24 June 2025
Line 1:		Line 1:
	{{Short description\|Specification for a Java platform application programming interface}}		{{Short description\|Specification for a Java platform application programming interface}}
	'''Content Repository API for Java''' ('''JCR''') is a specification for a [[Java (software platform)\|Java]] platform [[application programming interface]] (API) to access [[content repository\|content repositories]] in a uniform manner.<ref>~~[http~~://www.jcp.org/en/jsr/detail?id=93 ~~Java API for XML Registries]~~ - ~~Another Java API for Registries and Repositories~~</ref>{{failed verification\|date=December 2010}} The content repositories are used in content management systems to keep the content data and also the [[metadata]] used in [[content management system]]s (CMS) such as versioning metadata. The specification was developed under the [[Java Community Process]] as JSR-170 (Version 1),<ref>~~[http~~://www.jcp.org/en/jsr/detail?id=170 ~~JSR~~-~~170]~~</ref><ref>{{Cite web \|url=http://www.day.com/specs/jcr/1.0/ \|title=JSR-170 (HTML version of the specification) \|access-date=2009-02-17 \|archive-url=https://web.archive.org/web/20090608045548/http://www.day.com/specs/jcr/1.0/ \|archive-date=2009-06-08 \|url-status=dead }}</ref> and as JSR-283 (version 2).<ref>~~[http~~://jcp.org/en/jsr/detail?id=283 ~~JSR~~-~~283]~~</ref> The main [[Java package]] is <code>javax.jcr</code>.		'''Content Repository API for Java''' ('''JCR''') is a specification for a [[Java (software platform)\|Java]] platform [[application programming interface]] (API) to access [[content repository\|content repositories]] in a uniform manner.<ref>{{Cite web \|title=The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 93 \|url=https://www.jcp.org/en/jsr/detail?id=93 \|access-date=2025-06-24 \|website=www.jcp.org}}</ref>{{failed verification\|date=December 2010}} The content repositories are used in content management systems to keep the content data and also the [[metadata]] used in [[content management system]]s (CMS) such as versioning metadata. The specification was developed under the [[Java Community Process]] as JSR-170 (Version 1),<ref>{{Cite web \|title=The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 170 \|url=https://www.jcp.org/en/jsr/detail?id=170 \|access-date=2025-06-24 \|website=www.jcp.org}}</ref><ref>{{Cite web \|url=http://www.day.com/specs/jcr/1.0/ \|title=JSR-170 (HTML version of the specification) \|access-date=2009-02-17 \|archive-url=https://web.archive.org/web/20090608045548/http://www.day.com/specs/jcr/1.0/ \|archive-date=2009-06-08 \|url-status=dead }}</ref> and as JSR-283 (version 2).<ref>{{Cite web \|title=The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 283 \|url=https://jcp.org/en/jsr/detail?id=283 \|access-date=2025-06-24 \|website=jcp.org}}</ref> The main [[Java package]] is <code>javax.jcr</code>.

	== Overview ==		== Overview ==
Line 7:		Line 7:

	== Data structure ==		== Data structure ==
	The data in a JCR consists of a tree of nodes with associated properties. Data is stored in the properties, which may hold simple values such as numbers and strings or binary data of arbitrary length. Nodes may optionally have one or more types associated with them which dictate the kinds of properties, number and type of child nodes, and certain behavioral characteristics of the nodes. Nodes may point to other nodes via a special reference type property. In this way nodes in a JCR offer both [[referential integrity]] and object-oriented concept of [[inheritance (object-oriented programming)\|inheritance]]. Additional node types include the referenceable node type which allows the user to reference said node through use of a universally unique identifier. Another popular type is the versionable type. This makes the repository track a document's history and store copies of each version of the document.		The data in a JCR consists of a tree of nodes with associated properties. Data is stored in the properties, which may hold simple values such as numbers and strings or binary data of arbitrary length. Nodes may optionally have one or more types associated with them which dictate the kinds of properties, number, and type of child nodes, and certain behavioral characteristics of the nodes. Nodes may point to other nodes via a special reference type property. In this way, nodes in a JCR offer both [[referential integrity]] and the object-oriented concept of [[inheritance (object-oriented programming)\|inheritance]]. Additional node types include the referenceable node type, which allows the user to reference said node through use of a universally unique identifier. Another popular type is the versionable type. This makes the repository track a document's history and store copies of each version of the document.

	== Queries ==		== Queries ==
	A JCR can export portions of its tree to XML in two standard formats and can import hierarchies directly from XML. JSR 283 compliant implementations must support a standardized form of [[SQL]] for queries and a query object model QOM. JSR 283 deprecates the [[XPath]] query language defined in JSR 170.		A JCR can export portions of its tree to XML in two standard formats and can import hierarchies directly from XML. JSR 283 compliant implementations must support a standardized form of [[SQL]] for queries and a query object model QOM. JSR 283 deprecates the [[XPath]] query language defined in JSR 170. The [[Apache Jackrabbit]] reference implementation of JCR also supports the integration of the [[Apache Lucene]] search engine to give full text searches of data in the repository.
	The [[Apache Jackrabbit]] reference implementation of JCR also supports the integration of the [[Apache Lucene]] search engine to give full text searches of data in the repository.

	== Available implementations ==		== Available implementations ==
	Both JSRs are led by [[David Nüscheler]] of [[Adobe Systems]] (formerly of [[Day Software]]). Day had both a commercial JCR implementation called Content Repository Extreme (CRX) and was involved in the open source [[Apache Jackrabbit]] JCR,<ref>~~[http~~://jackrabbit.apache.org ~~Apache Jackrabbit home page]~~</ref><ref>~~[http~~://~~wiki~~.apache.org/~~jackrabbit~~/~~JcrLinks JCR links] to articles and applications based on JCR~~.</ref> which had its 2.0 release in January 2010. ModeShape<ref>{{Cite web \|title=ModeShape 5.4.0.Final is available \|url=https://modeshape.jboss.org/ \|access-date=2024-05-30 \|website=modeshape.jboss.org}}</ref> is another open source JCR implementation that supports JSR-283. [[Adobe_Experience_Cloud\|Adobe Experience Manager (AEM)]], [[Jahia]], [[Hippo CMS]] and [[Magnolia (CMS)\|Magnolia]] are Enterprise Content Management systems built on the JCR API, using Jackrabbit as its repository by default, but able to plug in any other JSR-170 certified repository implementation. JSR-170 is also supported by [[Oracle Beehive]], Oracle's enterprise collaboration software. The eXo JCR by eXo Platform is an open source repository with paid commercial support and documentation. Many other commercial vendors are working on JCR compatibility and products. [[Alfresco (software)\|Alfresco]] is an open source content management system which provides a JCR API onto their repository. GX released the new ~~[[GX WebManager Community Edition\|~~community version]] of its Web [[enterprise content management]] (ECM) platform based natively on [[Apache Jackrabbit]] and JSR.		Both JSRs are led by David Nüscheler of [[Adobe Systems]] (formerly of [[Day Software]]). Day had both a commercial JCR implementation called Content Repository Extreme (CRX) and was involved in the open source [[Apache Jackrabbit]] JCR,<ref>{{Cite web \|title=Apache Jackrabbit – Welcome to Apache Jackrabbit \|url=https://jackrabbit.apache.org/jcr/index.html \|access-date=2025-06-24 \|website=jackrabbit.apache.org}}</ref><ref>{{Cite web \|title=Log In - Apache Software Foundation \|url=https://cwiki.apache.org/confluence/login.action?os_destination=%2Fpages%2Fviewpage.action%3FspaceKey%3Djackrabbit%26title%3DJcrLinks&permissionViolation=true \|access-date=2025-06-24 \|website=cwiki.apache.org}}</ref> which had its 2.0 release in January 2010. ModeShape<ref>{{Cite web \|title=ModeShape 5.4.0.Final is available \|url=https://modeshape.jboss.org/ \|access-date=2024-05-30 \|website=modeshape.jboss.org}}</ref> is another open source JCR implementation that supports JSR-283. [[Adobe_Experience_Cloud\|Adobe Experience Manager (AEM)]], [[Jahia]], [[Hippo CMS]] and [[Magnolia (CMS)\|Magnolia]] are Enterprise Content Management systems built on the JCR API, using Jackrabbit as its repository by default, but able to plug in any other JSR-170 certified repository implementation. JSR-170 is also supported by [[Oracle Beehive]], Oracle's enterprise collaboration software. The eXo JCR by eXo Platform is an open source repository with paid commercial support and documentation. Many other commercial vendors are working on JCR compatibility and products. [[Alfresco (software)\|Alfresco]] is an open source content management system which provides a JCR API onto their repository. GX released the new community version of its Web [[enterprise content management]] (ECM) platform, based natively on [[Apache Jackrabbit]] and JSR.

	PHP adaptions have been started by [[TYPO3]], translating the Java API to PHP.<ref>~~[http~~://~~forge~~.~~typo3.org~~/~~projects~~/~~package~~-~~phpcr phpCR]~~</ref><ref>~~[https~~://~~github~~.~~com~~/~~phpcr~~/phpcr ~~phpcr on github]~~</ref> The [[PHPCR]] interfaces are also implemented by Jackalope,<ref>{{Cite web \|url=https://jackalope.github.com/ \|title=Jackalope: JCR for PHP \|access-date=2017-09-19 \|archive-date=2013-01-27 \|archive-url=https://web.archive.org/web/20130127183600/http://jackalope.github.com/ \|url-status=dead }}</ref> a PHP frontend talking to the Jackrabbit backend through the WebDAV interface, and [[Midgard (software)\|Midgard]],<ref>{{cite news\|title=Midgard2 PHPCR provider hits 1.0\|first=Henri\|last=Bergius\|url=http://bergie.iki.fi/blog/midgard2_phpcr_provider_hits_1-0/\|date=2011-12-23}}</ref> a cross-language content repository.		PHP adaptions have been started by [[TYPO3]], translating the Java API to PHP.<ref>{{Citation \|title=phpcr/phpcr \|date=2025-05-23 \|url=https://github.com/phpcr/phpcr \|access-date=2025-06-24 \|publisher=PHPCR}}</ref><ref>{{cite web \|title=PHPCR Package – TYPO3 Forge \|url=http://forge.typo3.org/projects/package-phpcr \|access-date=2025-06-24 \|website=TYPO3 Forge}}</ref>The PHPCR interfaces are also implemented by Jackalope,<ref>{{Cite web \|url=https://jackalope.github.com/ \|title=Jackalope: JCR for PHP \|access-date=2017-09-19 \|archive-date=2013-01-27 \|archive-url=https://web.archive.org/web/20130127183600/http://jackalope.github.com/ \|url-status=dead }}</ref> a PHP frontend talking to the Jackrabbit backend through the WebDAV interface, and [[Midgard (software)\|Midgard]],<ref>{{cite news\|title=Midgard2 PHPCR provider hits 1.0\|first=Henri\|last=Bergius\|url=http://bergie.iki.fi/blog/midgard2_phpcr_provider_hits_1-0/\|date=2011-12-23}}</ref> a cross-language content repository.

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

imported>0i burabo noi 5 at 14:13, 30 May 2024

2024-05-30T14:13:16Z

New page

{{Short description|Specification for a Java platform application programming interface}}
'''Content Repository API for Java''' ('''JCR''') is a specification for a [[Java (software platform)|Java]] platform [[application programming interface]] (API) to access [[content repository|content repositories]] in a uniform manner.<ref>[http://www.jcp.org/en/jsr/detail?id=93 Java API for XML Registries] - Another Java API for Registries and Repositories</ref>{{failed verification|date=December 2010}} The content repositories are used in content management systems to keep the content data and also the [[metadata]] used in [[content management system]]s (CMS) such as versioning metadata. The specification was developed under the [[Java Community Process]] as JSR-170 (Version 1),<ref>[http://www.jcp.org/en/jsr/detail?id=170 JSR-170]</ref><ref>{{Cite web |url=http://www.day.com/specs/jcr/1.0/ |title=JSR-170 (HTML version of the specification) |access-date=2009-02-17 |archive-url=https://web.archive.org/web/20090608045548/http://www.day.com/specs/jcr/1.0/ |archive-date=2009-06-08 |url-status=dead }}</ref> and as JSR-283 (version 2).<ref>[http://jcp.org/en/jsr/detail?id=283 JSR-283]</ref> The main [[Java package]] is <code>javax.jcr</code>.

== Overview ==
A JCR is a type of [[object database]] tailored to storing, searching, and retrieving hierarchical data. The JCR API grew out of the needs of content management systems, which require storing documents and other binary objects with associated metadata; however, the API is applicable to many additional types of applications. In addition to object storage, the JCR provides: APIs for versioning of data; [[database transaction|transactions]]; observation of changes in data; and import or export of data to [[XML]] in a standard way.
{{Further|Jcrom}}

== Data structure ==
The data in a JCR consists of a tree of nodes with associated properties. Data is stored in the properties, which may hold simple values such as numbers and strings or binary data of arbitrary length. Nodes may optionally have one or more types associated with them which dictate the kinds of properties, number and type of child nodes, and certain behavioral characteristics of the nodes. Nodes may point to other nodes via a special reference type property. In this way nodes in a JCR offer both [[referential integrity]] and object-oriented concept of [[inheritance (object-oriented programming)|inheritance]]. Additional node types include the referenceable node type which allows the user to reference said node through use of a universally unique identifier. Another popular type is the versionable type. This makes the repository track a document's history and store copies of each version of the document.

== Queries ==
A JCR can export portions of its tree to XML in two standard formats and can import hierarchies directly from XML. JSR 283 compliant implementations must support a standardized form of [[SQL]] for queries and a query object model QOM. JSR 283 deprecates the [[XPath]] query language defined in JSR 170.
The [[Apache Jackrabbit]] reference implementation of JCR also supports the integration of the [[Apache Lucene]] search engine to give full text searches of data in the repository.

== Available implementations ==
Both JSRs are led by [[David Nüscheler]] of [[Adobe Systems]] (formerly of [[Day Software]]). Day had both a commercial JCR implementation called Content Repository Extreme (CRX) and was involved in the open source [[Apache Jackrabbit]] JCR,<ref>[http://jackrabbit.apache.org Apache Jackrabbit home page]</ref><ref>[http://wiki.apache.org/jackrabbit/JcrLinks JCR links] to articles and applications based on JCR.</ref> which had its 2.0 release in January 2010. ModeShape<ref>{{Cite web |title=ModeShape 5.4.0.Final is available |url=https://modeshape.jboss.org/ |access-date=2024-05-30 |website=modeshape.jboss.org}}</ref> is another open source JCR implementation that supports JSR-283. [[Adobe_Experience_Cloud|Adobe Experience Manager (AEM)]], [[Jahia]], [[Hippo CMS]] and [[Magnolia (CMS)|Magnolia]] are Enterprise Content Management systems built on the JCR API, using Jackrabbit as its repository by default, but able to plug in any other JSR-170 certified repository implementation. JSR-170 is also supported by [[Oracle Beehive]], Oracle's enterprise collaboration software. The eXo JCR by eXo Platform is an open source repository with paid commercial support and documentation. Many other commercial vendors are working on JCR compatibility and products. [[Alfresco (software)|Alfresco]] is an open source content management system which provides a JCR API onto their repository. GX released the new [[GX WebManager Community Edition|community version]] of its Web [[enterprise content management]] (ECM) platform based natively on [[Apache Jackrabbit]] and JSR.

PHP adaptions have been started by [[TYPO3]], translating the Java API to PHP.<ref>[http://forge.typo3.org/projects/package-phpcr phpCR]</ref><ref>[https://github.com/phpcr/phpcr phpcr on github]</ref> The [[PHPCR]] interfaces are also implemented by Jackalope,<ref>{{Cite web |url=https://jackalope.github.com/ |title=Jackalope: JCR for PHP |access-date=2017-09-19 |archive-date=2013-01-27 |archive-url=https://web.archive.org/web/20130127183600/http://jackalope.github.com/ |url-status=dead }}</ref> a PHP frontend talking to the Jackrabbit backend through the WebDAV interface, and [[Midgard (software)|Midgard]],<ref>{{cite news|title=Midgard2 PHPCR provider hits 1.0|first=Henri|last=Bergius|url=http://bergie.iki.fi/blog/midgard2_phpcr_provider_hits_1-0/|date=2011-12-23}}</ref> a cross-language content repository.

== See also ==
* [[Content Management Interoperability Services]] (CMIS), another content repository API

== References ==
{{Reflist|30em}}

[[Category:Java enterprise platform]]
[[Category:Java specification requests]]
[[Category:Content management systems]]
[[Category:Database management systems]]