[
https://issues.apache.org/jira/browse/OAK-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706774#comment-13706774
]
Alex Parvulescu commented on OAK-898:
-------------------------------------
makes sense, I've tweaked the test to make it closer to what happens behind the
scenes in my failing scenario: removed the failing assert (as Jukka mentioned
it was not an issue), and added a getNode call with a new session which fails
with a _PathNotFoundException_.
Worth to mention that the failure I see is based on the _@MoveFrom_
functionality from the sling post servlet, and I think all the steps outlined
in the provided test are done via http POST calls using new sessions, that's
why I'm having a bit of a hard time reproducing this in a pure oak environment.
For reference, here are some sling integration tests that cover these bits.
[0]
http://svn.apache.org/viewvc/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/PostServletAtMoveTest.java?view=markup#l37
> Session#move with a fresh session doesn't work properly
> -------------------------------------------------------
>
> Key: OAK-898
> URL: https://issues.apache.org/jira/browse/OAK-898
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Alex Parvulescu
>
> The scenario is as follows: create a node, then try to move it using a new
> session.
> Will attach a test case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
