hi,
the rmi implementation is jcr neutral, if you don't want to use RMI, you need to run your application in the same VM as the repository. the problem is, that jsr170 does not specify any remoting protocol. but this will change in jsr283 (jcr2.0) which defines (among other new stuff) a SPI.
JCR is an API and as much as JDBC does not specify a transport protocol JCR should not do that either. The expert group of JSR-283 decided that the SPI is out of scope for the core JCR spec and that's also why the development of the SPI is progressing very quickly as a part of the Jackrabbit project. I very much agree with this decision. As Tobi mentioned there is an option of remoting JCR through RMI as one option in Jackrabbit. The SPI contrib also offers a remoting through WebDAV as an alternative way of communicating a JCR client with a Jackrabbit Instance. regards, david
