> How I can define a workspace that is not in the same machine > the webapp is running?
That's what the JCR-RMI code is for. You have a JCR-RMI "server" that runs a Jackrabbit repository (or more than one) and makes it (or them) available via RMI. In your webapp, instead of calling jackrabbit code directly, you call the JCR-RMI client code to obtain your initial repository object. From then on, it all looks the same as direct Jackrabbit (or any other JSR-170) access, just slower. I'd advise you to look up the jcr-rmi code, documentation etc. The subject was covered in this mailing list some months ago, so searching through this mailing list for "RMI" should pick up useful messages. Note: RMI isn't the only option - you could probably use CORBA, HTTP or anything else you wanted as it should be possible to make a client and server wrapper (for JSR-170) that works with any protocol you care to use, but as far as I am aware, RMI is the only protocol that's already been done, so if you're after a "ready to use" method of putting the repository on a different machine, RMI is the thing to use. _____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
