| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
Beginning in version R28, XperienCentral no longer uses the Apache Jackrabbit JCR indexing solution by default. This topic is only relevant to users of XperienCentral versions R27 and lower or if you configure XperienCentral to use Apache Jackrabbit. See The XperienCentral JCR Index for more information. |
The JCR browser is a tool for exploring the Java Content Repository (JCR) used by XperienCentral to store website data. It allows you to browse through the repository by expanding/collapsing sub trees in the same way as with File Explorer in Microsoft Windows. You can perform the following operations on JCR tree items:
...
Due to node type definitions, the JCR browser cannot perform all operations on every node. If you try to create an improper child node or property, the JCR browser will return an error. Additonally, you can perform queries on the JCR tree. With queries you can search for specific content. The JCR browser supports the XPath and SQL syntaxes.
| Info |
|---|
See also Xpath JCR Sample Queries. |
| Warning |
|---|
Some of the actions you can take perform in the JCR Browser, such as deleting nodes and/or their attributes or properties could have an adverse affect on your website. Be especially careful when performing such actions. |
...
In This Topic
| Table of Contents | ||
|---|---|---|
|
...
Introduction to JCR
...
| Expand | ||
|---|---|---|
| ||
A Java Content Repository (JCR) is a database with a standardized Java Application Programming Interface (API). A JCR allows different applications to access one centralized database. Other technologies that are comparable to JCR are JDBC, Hibernate and WebDAV. Unlike relational databases, a JCR has a hierarchical tree structure. The tree consists of nodes and properties. The properties are the leaves of the tree and represent the actual pieces of database content. A property is of one of the following types: string, binary, date, a number type, boolean, name, path or reference.
 In addition, a node contains attributes that are related to the node itself, for example the name of the node, its path in the tree, its depth in the tree and its type. Therefore, a node has attributes and it contains properties. The organization of the repository into a tree structure is done by the JCR Browser: Internally the content may be stored in a relational database. Node TypesEvery node has one primary node type. The primary node type defines the properties and child nodes that it is allowed or required to have. Every node has a special property called Multi-value PropertiesIn some cases, a property may have more than one value. A property that may have more than one value is referred to as a multi-value property. The property definition determines whether a particular property is a multi-value property. Standardized by JCPJCR has been standardized by the Java Community Process (JCP) in JSR 170 (API version 1.0) and JSR 283 (API version 2.0). Depending on the API version and compliance level, a JCR may support the following:
|
...
Using the XperienCentral JCR Browser
...
When you select a node, the following attributes are shown in the "Node Attributes" section:
| Attribute | Description |
|---|---|
| Name | The name of the node. |
| Value (primary item) | This attribute is not used in XperienCentral. It is "undefined" for all nodes. |
| Path | The path the node belongs to. This is relative to the depth 1 parent mode of the current node. The root node is not shown in the path. |
| UUID | The hexadecimal identifier of the node, 1b8c88d37f0000020084433d3af4941f, for example. |
| Depth | The depth of the node relative to the root node. The first depth is 1. The depth of the root node is 0 and is the only node with this value. |
| Primary node type | The node's type. See http://jackrabbit.apache.org/jcr/node-types.html for an explanation of the possible node types. |
...
When you select a node, the following attributes are shown in the "Node Properties" section:
| Property | Description |
|---|---|
| Name | The name of the node. |
| Type | This attribute is not used in XperienCentral. It is "undefined" for all nodes. |
| Value | The path the node belongs to. This is relative to the depth 1 parent mode of the current node. The root node is not shown in the path. |
| DeleteUUID | The hexadecimal identifier of the node, 1b8c88d37f0000020084433d3af4941f, for example. |
| Depth | The depth of the node relative to the root node. The first depth is 1. The depth of the root node is 0 and is the only node with this value. |
| Primary node type | The node's type. See http://jackrabbit.apache.org/jcr/node-types.html for an explanation of the possible node types. |
...
If a property is a reference in the JCR tree, its value is shown as a link. Click on the link to navigate to the referenced node in the JCR tree. For example:
...
Operations with Nodes
Creating a Node
...
- Select the node to be deleted.
- Click [Delete] in the "Actions" section. You are prompted to confirm the action.
- Click [OK]. The node, including its properties and subtrees, are deleted.
...
Operations with Node Properties
...
- Select the "Delete" checkbox next to the property to be deleted.
- Click [Delete]. You are prompted to confirm.
- Click [OK]. The property is deleted.
...
...
Executing JCR Queries
By way of example, the JCR browser is provided with a list of pre-programmed XPath and SQL queries. To this list, you can add your own queries. Your queries are saved and you can edit them at a later time. To execute a query, you just select one from the list, modify it and then execute it.
...
Query Examples: SQL Versus XPath
| SQL | XPath |
|---|---|
SELECT * FROM nt:base | //* |
SELECT * FROM my:type | //element(*, my:type) |
SELECT my:title FROM my:type | //element(*, my:type)/@my:title |
SELECT my:title, my:text FROM my:type | //element(*, my:type)/ (@my:title | @my:text) |
SELECT * FROM my:type WHERE jcr:path LIKE '/nodes[%]/%' | /jcr:root/nodes// element(*, my:type) |
SELECT * FROM my:type WHERE my:title='JSR 170' | //element(*, my:type) [@my:title = 'JSR 170'] |
SELECT * FROM my:type WHERE my:title <> 'JSR 170' | //element(*, my:type) [@my:title != 'JSR 170'] |
SELECT * FROM my:type WHERE my:title = 'JSR 170' AND my:author = 'David' | //element(*, my:type) [@my:title = 'JSR 170' and @my:author = 'David'] |
SELECT * FROM my:type WHERE NOT (my:title = 'JSR 170') | //element(*, my:type) [not(@my:title = 'JSR 170')] |
SELECT * FROM my:type WHERE my:title IS NOT NULL | //element(*, my:type) [@my:title] |
SELECT * FROM my:type WHERE my:title IS NULL | //element(*, my:type) [not(@my:title)] |
SELECT * FROM my:type WHERE my:title LIKE 'JSR 170%' | //element(*, my:type) [jcr:like(@my:title, 'JSR 170%')] |
SELECT * FROM my:type WHERE CONTAINS(*, 'JSR 170') | //element(*, my:type) [jcr:contains(., 'JSR 170')] |
SELECT * FROM my:type WHERE jcr:path LIKE'/some[%]/nodes[%]' | /jcr:root/some/ element(nodes, my:type) |
SELECT * FROM my:type WHERE jcr:path = '/some/nodes' | /jcr:root/some[1]/element(nodes, my:type)[1] |
SELECT * FROM my:type WHERE jcr:path LIKE '/some[%]/nodes[%]/%' AND NOT jcr:path LIKE '/some[%]/nodes[%]/%/%' | /jcr:root/some/nodes/ element(*, my:type) |
SELECT * FROM my:type WHERE jcr:path LIKE '/some/nodes/%' AND NOT jcr:path LIKE '/some/nodes/%/%' | /jcr:root/some[1]/nodes[1]/ element(*, my:type) |
SELECT * FROM my:type WHERE jcr:path LIKE '/some[%]/nodes[%]/%' | /jcr:root/some/nodes// element(*, my:type) |
SELECT * FROM my:type WHERE jcr:path LIKE '/some/nodes/%' | /jcr:root/some[1]/nodes[1]// element(*, my:type) |
SELECT * FROM my:type WHERE jcr:path LIKE '/some[%]/nodes[%]' OR jcr:path LIKE '/some[%]/nodes[%]/%' | /jcr:root/some/nodes// element(*, my:type) |
SELECT * FROM my:type WHERE jcr:path = '/some/nodes' OR jcr:path LIKE '/some/nodes/%' | /jcr:root/some[1]/nodes[1]// element(*, my:type) |
Deleting a Query from the List
...
- Select the JCR Browser tab.
- Click [More]. The "Query execution" section appears.
- Select the query, for instance "MyNodeTypes XPath", from the drop-down list.
- Modify the query to your needs.
- Click [Execute query]. The results appear on the Query results tab.