[ http://issues.apache.org/jira/browse/JCR-321?page=all ]
Adam Warski updated JCR-321:
----------------------------
Attachment: JcrSessionTest.java
Source code for the problematic case.
> Information about new nodes isn't propagated through repositories.
> ------------------------------------------------------------------
>
> Key: JCR-321
> URL: http://issues.apache.org/jira/browse/JCR-321
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 0.9
> Environment: Jackrabbit SVN head version
> Reporter: Adam Warski
> Attachments: JcrSessionTest.java
>
> Here's what I'm doing:
> 1. Create 2 repositories
> 2. Create a new node, using repository1
> 3. List nodes, using repository2 - the new node _is not_ there!
> 4. List nodes, using repository1 - the new node _is_ there
> 5. Create a new repository and list nodes - again, the node is there
> So it seems that the repository1 doesn't notice the new node - I would expect
> a different behaviour, but maybe it's intentional? How can I make repo1 see
> the new node?
> I attach a java file which runs the case I described.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
