Andreas this looks pretty weird.
Have you tried this scenario:
1/ logout (meaning you close all your browser windows => your user session is killed and so the jcr
session)
2/ relogin
You should definitely see the changes after doing this.
Another problem may be that the external tool is opening a transaction and never commits it, so the
new modifications are only transient.
./alex
--
.w( the_mindstorm )p.
#: (Andreas Brenk) changed the world a bit at a time by saying on 11/7/2005
12:41 PM :#
Hi,
in a current project the website repository Magnolia uses gets
modified by another part of the application that directly accesses the
JCR API. The Magnolia adminCentral is not used to modify content. My
problem now is: Magnolia only sees the repository as it was when the
server was started. No modifications made during the same server
runtime show up. Wether they are moved nodes / pages or updated
paragraphs. Only a server restart makes these changes visible.
I already tried modifying the Magnolia code in several places and
calling Session#refresh() or Item#refresh() but my changes don't show
up. I read section 7.1.3.4 ("Seeing Changes Made by Other Sessions")
of the JCR spec over and over again but to no avail.
The project started with Magnolia 2.1 and Jackrabbit's
ObjectPersistenceManager but was recently upgraded to Magnolia 2.1.3
and BerkeleyDBPersistenceManager.
Any help is greatly appreciated as I'm really stuck and running out of
ideas. Further details will be happily provided on request.
Thanks in advance,
Andreas
--
Andreas Brenk
[EMAIL PROTECTED]
http://andreasbrenk.com/
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
