jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-321) Information about new nodes isn't propagated through repositories.
Date Wed, 15 Feb 2006 21:46:10 GMT
     [ http://issues.apache.org/jira/browse/JCR-321?page=all ]
     
Jukka Zitting resolved JCR-321:
-------------------------------

    Resolution: Invalid

Jackrabbit doesn't support simultaneous access to the same repository data from different
repository instances. You can only run a single repository instance at a time on a given repository
home directory. There should actually be a lock file that prevents two instances from accessing
the repository at the same time, thus preventing your test case, but there might be something
wrong with the locking mechanism.

Instead of using separate repository instances you should be using separate sessions of the
same repository. Changes made in one session will become visible in another session once the
first session calls Session.save().


> 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
>     Assignee: Jukka Zitting
>  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


Mime
View raw message