 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in org.apache.jackrabbit.usersRe: [jcr-rmi] How to configure for RM...| From | Sent On | Attachments |
|---|---|---|
| Markus Reis | Oct 19, 2007 12:15 am | |
| Mihai Anescu | Oct 19, 2007 12:24 am | |
| Markus Reis | Oct 19, 2007 12:30 am | |
| Markus Reis | Nov 5, 2007 2:14 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [jcr-rmi] How to configure for RMI-Lookup | Actions... |
|---|---|---|
| From: | Markus Reis (mark...@researchstudio.at) | |
| Date: | Nov 5, 2007 2:14:16 am | |
| List: | org.apache.jackrabbit.users | |
Dear All,
unfortunately I got no responses that brought me closer to a solution
... still I'm convinced that someone could easily help me here ... so
please have a quick look (original post:
http://mail-archives.apache.org/mod_mbox/jackrabbit-users/200710.mbox/%3c471859AD.9000001@researchstudio.at%3e).
many thanks, Markus
Markus Reis schrieb:
Hi Mihai,
that's exactly what I did (though with 1.3.1) and it works perfectly.
My original question was however different (RMI-Lookup instead of JNDI-Lookup - see my original post for details).
kind regards, Markus
Mihai Anescu schrieb:
Hello Markus,
To expose JR via RMI you need a RMI jar for JR: jackrabbit-jcr-rmi-1.3.jar (we're using JR 1.3, so the name may be different). You just copy it into the server/default/deploy/ folder of JBoss.
And that exposes a RemoteRepository. I guess you can change the endpoint...
Here's some code to try it:
Credentials cred = new SimpleCredentials("user", "pwd".toCharArray()); RemoteSession session = null;
Properties properties = new Properties(); properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); properties.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); properties.put(Context.PROVIDER_URL, "localhost:1099"); InitialContext ctx = new InitialContext(properties);
Object obj = ctx.lookup("jnp://localhost:1099/jcrServer");
RemoteRepository repo = (RemoteRepository) obj; session = repo.login(cred);
-----Original Message----- From: Markus Reis [mailto:mark...@researchstudio.at] Sent: Friday, October 19, 2007 10:16 AM To: use...@jackrabbit.apache.org Subject: [jcr-rmi] How to configure for RMI-Lookup
Hi,
as far as I understand, the jcr-rmi server configuration registers the server/repository via JNDI jackrabbit-rmi-service.xml: ... <attribute name="RemoteAddress">jnp://localhost:1099/jcrServer</attribute> ...
Some (unfortunately most) Jackrabbit/JCR clients (e.g.: http://www.day.com/eclipse/) however use classical RMI lookup ((RemoteRepository)Naming.lookup("rmi://localhost:1099/jcrServer");) in order to get a handle to the remote repository, which results in a "non-JRMP server at remote endpoint" java.rmi.ConnectIOException, due to
the fact that there's no traditional RMI registry running on 1099, but rather a JNDI registry.
Is it possible to change the configuration (in jackrabbit-rmi-service.xml?) so that the server-side/remote repository gets bound to a traditional RMI registry and if yes what do I have to change?
kind regards, Markus
PS: I'm working with jackrabbit 1.3.1 and JBoss 4.0.5
-- Mag. Markus Reis
Austrian Research Centers GmbH - ARC Research Studios Studio Digital Memory Engineering
Thurngasse 8/3/20, A-1090 Wien Mobile: +43 664 825 1106 Tel.: +43-1-585 05 37 - 16 Fax: +43-1-585 37 41
<mark...@researchstudio.at> http://www.arcs.ac.at/ http://www.researchstudio.at/ http://dme.researchstudio.at/
HG Wien – FN 115980i – ATU14703506