Ok Mathias, There's also one other thing I didn't think of (and haven't tried myself) which is that the MongoDB that is actually backing the DB could itself be remote, and then JCR instance can still talk to it (i think), so that would be interesting to see if that performs well at all or where the bottlenecks are if it doesn't. Also worth mentioning is that in meta64's approach the Spring REST controller (which is actually more of an RMI over JSON approach than a 'true REST') is a very easy service to be called either by Browsers --OR-- by other servers doing use plain JSON POSTS. I have that one class called
Best regards, Clay Ferguson [email protected] On Sun, Oct 23, 2016 at 9:48 AM, mathiasconradt <[email protected]> wrote: > Hi Clay, > > thanks for the link on StackOverflow. I came across this already, but the > JcrUtils.getRepository(url) method only seems to work for JackRabbit2, not > for Oak. At least in my tests. Thanks for pointing me to Sling. > > For the moment, I think I will also use the same approach as you with > meta64 > and embed Oak directly into the app and use the Java API. It thought about > it today and it actually makes more sense for what I want to do as well. > > - Mathias > > > > -- > View this message in context: http://jackrabbit.510166.n4. > nabble.com/How-to-connect-to-OAK-standalone-server-tp4663274p4665175.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >
