On 10/18/07, Markus Reis <[EMAIL PROTECTED]> wrote: > Hi Felix, > > > many thanks for your response. > > The problem - as I can see it - is that JBoss uses port 4444 as the > RMIObjectPort (see http://wiki.jboss.org/wiki/Wiki.jsp?page=JRMPInvoker > for details). The default Jackrabbit server implementation however > (tries to) bind(s) to port 1099 (although via the jnp protocol!) >
I think you are right, the class that registers the repository[1] and the xml file that declares the jboss mbean service[2] should be fixed. [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/java/org/apache/jackrabbit/rmi/server/jmx/JCRServer.java [2] http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/resources/jackrabbit-rmi-service.xml Feel free to create a jira issue. br, edgar > Could you either tell me whether > a) //localhost:1099/jcrServer works for you (if the repsitory is running > on JBoss - after you've set up this environment :-)) > b) what files I'd have to change (and how) in order to correctly > configure the RMI interface for the jackrabbit server side > > > many thanks, > Markus > > > Felix Meschberger schrieb: > > Hi Markus, > > > > Am Dienstag, den 16.10.2007, 14:48 +0200 schrieb Markus Reis: > > > >> Hi Felix, > >> > >> > >> if I try to connect (i.e. click on "Finish") to my jackrabbit repos > >> (running on jboss) via rmi://localhost:1099/jcrServer (I also tried > >> //localhost:1099/jcrServer in "Repository RMI URL" field), I get the > >> following exception: > >> javax.jcr.RepositoryException: non-JRMP server at remote endpoint: > >> non-JRMP server at remote endpoint > >> > > > > The correct URL is the one without the scheme, //localhost... that is. > > The name you add to the URL is the one used to register the Repository > > in the ServerAdapterFactory. If you enter //localhost:1099 in the URL > > field (provided your RMI registry is running on the default port 1099) > > you may click on the "Browse..." button to the right to get a list of > > repositories registered at the addressed RMI registry. > > > > Selecting one of those, should do the trick. > > > > > >> Client side: > >> CRX Feature for Eclipse, Version 3.5.1 > >> > > > > The most recent version is 3.6.2. You might want to update your feature > > from http://www.day.com/eclipse using the Eclipse Update Manager. > > > > > >> Did you already test with repositories running on JBoss? > >> > > > > To be honest, now :-) But this should actually not make a difference. If > > the repository is registered using the Jackrabbit RMI > > ServerAdapterFactory the standard Java RMI implementation should be > > used, which AFAIK is not different for JBoss. > > > > Hope this helps. > > > > Regards > > Felix > > > > > > > > > -- > 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 > > <[EMAIL PROTECTED]> > http://www.arcs.ac.at/ > http://www.researchstudio.at/ > http://dme.researchstudio.at/ > > HG Wien – FN 115980i – ATU14703506 > >
