[
https://issues.apache.org/jira/browse/CAMEL-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846433#comment-13846433
]
Gregor Zurowski edited comment on CAMEL-7064 at 12/12/13 5:36 PM:
------------------------------------------------------------------
The attached patch contains a new JUnit test "JcrProducerSubNodeTest" that
creates a node and a sub node in the same node hierarchy. It will fail if the
fix to JcrProducer (which is also part of the patch) is not applied.
I have also submitted a pull request for this fix:
https://github.com/apache/camel/pull/66
was (Author: gzurowski):
The attached patch contains a new JUnit test "JcrProducerSubNodeTest" that
creates a node and a sub node in the same node hierarchy. It will fail if the
fix to JcrProducer (which is also part of the patch) is not applied.
> JcrProducer ignores existing nodes and creates invalid node hierarchies
> -----------------------------------------------------------------------
>
> Key: CAMEL-7064
> URL: https://issues.apache.org/jira/browse/CAMEL-7064
> Project: Camel
> Issue Type: Bug
> Components: camel-jcr
> Reporter: Gregor Zurowski
> Attachments: camel-jcr-existing-nodes.patch
>
>
> The CamelJcrInsert operation of the JcrProducer does not handle existing
> nodes properly: If some of the nodes already exist within the path provided
> by the CamelJcrNodeName property, they will be skipped, resulting in the
> creation of an incorrect node hierarchy. Therefore, JcrProducer only works
> correctly with newly created node hierarchies.
> E.g.: For the requested path "/exists1/exists2/new-node", JcrProducer will
> incorrectly create "/new-node" (i.e. directly on root level), given nodes
> "exists1" and "exists2" do already exist in the repository.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
