Thanks Edouard, as you i started to think that it was not the behavior i wanted to achieve, which is the following:
Java applications HTTP clients accessing concurrently ====> JR Repo <==== GETTING [and to the repository PUTTING] resources - Can this be achieved with both the Standalone JR version and the WAR version? - Is it mandatory for concurrent access to get the repository object through a servlet? Thanks again! 2011/7/28 Edouard Hue <[email protected]> > If I got it well, what you do is starting simultaneously : > - one jackrabbit-standalone instance with --conf /path/to/repository.xml > - one or more instances of your application, which uses "new > TransientRepository("/path/to/repository.xml")" > This gives you at least two different running instances of Jackrabbit using > the same configuration, which is probably not what you intended to do. You > cannot have multiple instances sharing the same configuration. Either you > should use Jackrabbit's remote APIs (DAV or RMI) to connect to the > standalone instance, or stop using Jackrabbit standalone and start the > repository in your application code only. > > On Thu, Jul 28, 2011 at 1:02 PM, Francisco Carriedo Scher < > [email protected]> wrote: > >> Hi there, >> >> during the last days i have been writing an API (which abstracts file >> system >> operations, hidding the complexity of nodes and trees) to handle >> Jackrabbit >> repository from Java (repositories, sessions and so on...). >> >> The problem is that now, i want to access it concurrently both through my >> API and through URLs to the files (previously uploaded through my API) and >> i >> can not even start the interactive console mode (--cli ...) when the >> standalone server is running (existining lock...). >> >> I performed a very simple test to confirm that concurrent users are >> allowed: >> two browsers populating the repository concurrently, another one searching >> and so on... So, performance aside, concurrent users are supported. I have >> been checking aswell the populate.jsp and browse.jsp files in order to >> check >> how get they the concurrent access Java code to the repo and the it is >> quite >> similar to mine (from the API) but for how they instantiate the >> repository: >> >> *JSPs code* >> rep = >> RepositoryAccessServlet.getRepository(pageContext.getServletContext()); >> >> *My code* >> rep = new TransientRepository(); >> >> So, the questions for me are: >> >> - is it enough to get concurrent access to a running repository (fired up >> with *java -jar jackrabbit-standalone-2.2.7.jar --repo >> C:\Users\fcarriedo\workspace\filerepository\ --conf >> C:\path\to\repository\repository.xml*) to deploy my own servlets and >> instantiate the repository as the .jsp files do? >> >> - since no Servlet context can be obtained in little my API (which uses >> simple java classes), how should i obtain a Repository object to access it >> concurrently? >> >> Thanks in advance, even for reading so far... Greetings! >> > >
