...
The repository
element of the URI is used to look up the JCR Repository
object in the Camel context registry.
Producer
Div |
---|
class | confluenceTableSmall |
---|
|
Name | Default Value | Description |
---|
CamelJcrOperation
| CamelJcrInsert
| CamelJcrInsert or CamelJcrGetById operation to use | CamelJcrNodeName
| null
| Used to determine the node name to use. | CamelJcrNodeType | null | Camel 2.16: To use a specify primary node type when creating adding a new node. |
|
Wiki Markup |
---|
{div:class=confluenceTableSmall}
|| Name || Default Value || Description ||
| {{CamelJcrOperation}} | {{CamelJcrInsert}} | CamelJcrInsert or CamelJcrGetById operation to use |
| {{CamelJcrNodeName}} | {{null}} | Used to determine the node name to use. |
{div} |
When a message is sent to a JCR producer endpoint:
...
The consumer will connect to JCR periodically and return a List<javax.jcr.observation.Event> in the message body.
Div |
---|
class | confluenceTableSmall |
---|
|
Name | Default Value | Description |
---|
eventTypes
| 0
| A combination of one or more event types encoded as a bit mask value such as |
|
Wiki Markup |
---|
{div:class=confluenceTableSmall}
|| Name || Default Value || Description ||
| {{eventTypes}} | {{0}} | A combination of one or more event types encoded as a bit mask value such as javax.jcr.observation.Event.NODE_ADDED, |
javax.jcr.observation.Event.NODE_REMOVED, |
|
| {{deep}} | {{false}} | When it is true, events whose associated parent node is at current path or within its subgraph are received. |
| {{uuids}} | {{null}} | Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received.|
| {{nodeTypeNames}} | {{null}} | Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received. |
| {{noLocal}} | {{false}} | If {{noLocal}} is {{true}}, then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored. |
| {{sessionLiveCheckInterval}} | {{60000}} | Interval in milliseconds to wait before each session live checking. |
| {{sessionLiveCheckIntervalOnStart}} | {{3000}} | Interval in milliseconds to wait before the first session live checking. |
{div} | deep
| false
| When it is true, events whose associated parent node is at current path or within its subgraph are received. | uuids
| null
| Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received. | nodeTypeNames
| null
| Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received. | noLocal
| false
| If noLocal is true , then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored. | sessionLiveCheckInterval
| 60000
| Interval in milliseconds to wait before each session live checking. | sessionLiveCheckIntervalOnStart
| 3000
| Interval in milliseconds to wait before the first session live checking. | username | | Camel 2.15: Allows to specify the username as a uri parameter instead of in the authority section of the uri | password | | Camel 2.15: Allows to specify the password as a uri parameter instead of in the authority section of the uri | workspaceName | null
| Camel 2.16: Allows to specify a workspace different from default |
|
Example
The snippet below creates a node named node
under the /home/test
node in the content repository. One additional property is added to the node as well: my.contents.property
which will contain the body of the message being sent.
...