You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by greeklinux <ma...@gmx.net> on 2009/02/18 12:50:44 UTC

Jackrabbit 1.5.2 Standalone Problem

Hello,

I am trying to get Jackrabbit running as standalone server for Tests.
But I have the problem, that I can not create a connection. 

I open http://localhost:8080/ and I get the JCR server page. Under the
"remote access"
section I found the info, that I can access the repository over

RMI registry: //localhost/jackrabbit.repository

I tried with rmiregistry and without.

So why is this not possible.
I like Java and I think it is a great platform, but a lot of times it is
really hard to get something
running without to have to read about a new "abbreviation". I think you get
the point....

with best regards

-- 
View this message in context: http://www.nabble.com/Jackrabbit-1.5.2-Standalone-Problem-tp22077018p22077018.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Jackrabbit 1.5.2 Standalone Problem

Posted by greeklinux <ma...@gmx.net>.
Hello,

thanks for this tip. I start
rmiregistry -J-cp
-Jjackrabbit-api-1.5.0.jar:jcr-1.0.jar:jackrabbit-jcr-rmi-1.5.0.jar

and after that the standalone jar.

Now the rmi connection is found and I can connect over Spring and JCR
Eclipse plugin
from day software.

I think it would be good to give this hint on the rmi page.

best regards



Jukka Zitting wrote:
> 
> Hi,
> 
> On Wed, Feb 18, 2009 at 12:50 PM, greeklinux <ma...@gmx.net> wrote:
>> I open http://localhost:8080/ and I get the JCR server page. Under the
>> "remote access"
>> section I found the info, that I can access the repository over
>>
>> RMI registry: //localhost/jackrabbit.repository
>>
>> I tried with rmiregistry and without.
> 
> The rmiregistry needs to be running (with the jcr, jackrabbit-api, and
> jackrabbit-jcr-rmi jars in it's classpath) before you start the
> Jackrabbit standalone server. Otherwise the standalone server fails to
> register the RMI endpoint in the registry.
> 
> An easier alternative for accessing the repository remotely is to
> download the RMI endpoint directly from http://localhost:8080/rmi. You
> can use the URLRemoteRepository class to do this in your client code:
> 
>     import org.apache.jackrabbit.rmi.repository.URLRemoteRepository;
>     Repository repository = new
> URLRemoteRepository("http://localhost:8080/rmi");
> 
> BR,
> 
> Jukka Zitting
> 
> 

-- 
View this message in context: http://www.nabble.com/Jackrabbit-1.5.2-Standalone-Problem-tp22077018p22078461.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Jackrabbit 1.5.2 Standalone Problem

Posted by greeklinux <ma...@gmx.net>.
Hello,

thanks for this tip. I start
rmiregistry -J-cp
-Jjackrabbit-api-1.5.0.jar:jcr-1.0.jar:jackrabbit-jcr-rmi-1.5.0.jar

and after that the standalone jar.

Now the rmi connection is found and I can connect over Spring and JCR
Eclipse plugin
from day software.

I think it would be good to give this hint on the rmi page.

best regards



Jukka Zitting wrote:
> 
> Hi,
> 
> On Wed, Feb 18, 2009 at 12:50 PM, greeklinux <ma...@gmx.net> wrote:
>> I open http://localhost:8080/ and I get the JCR server page. Under the
>> "remote access"
>> section I found the info, that I can access the repository over
>>
>> RMI registry: //localhost/jackrabbit.repository
>>
>> I tried with rmiregistry and without.
> 
> The rmiregistry needs to be running (with the jcr, jackrabbit-api, and
> jackrabbit-jcr-rmi jars in it's classpath) before you start the
> Jackrabbit standalone server. Otherwise the standalone server fails to
> register the RMI endpoint in the registry.
> 
> An easier alternative for accessing the repository remotely is to
> download the RMI endpoint directly from http://localhost:8080/rmi. You
> can use the URLRemoteRepository class to do this in your client code:
> 
>     import org.apache.jackrabbit.rmi.repository.URLRemoteRepository;
>     Repository repository = new
> URLRemoteRepository("http://localhost:8080/rmi");
> 
> BR,
> 
> Jukka Zitting
> 
> 

-- 
View this message in context: http://www.nabble.com/Jackrabbit-1.5.2-Standalone-Problem-tp22077018p22078460.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Jackrabbit 1.5.2 Standalone Problem

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Feb 18, 2009 at 12:50 PM, greeklinux <ma...@gmx.net> wrote:
> I open http://localhost:8080/ and I get the JCR server page. Under the
> "remote access"
> section I found the info, that I can access the repository over
>
> RMI registry: //localhost/jackrabbit.repository
>
> I tried with rmiregistry and without.

The rmiregistry needs to be running (with the jcr, jackrabbit-api, and
jackrabbit-jcr-rmi jars in it's classpath) before you start the
Jackrabbit standalone server. Otherwise the standalone server fails to
register the RMI endpoint in the registry.

An easier alternative for accessing the repository remotely is to
download the RMI endpoint directly from http://localhost:8080/rmi. You
can use the URLRemoteRepository class to do this in your client code:

    import org.apache.jackrabbit.rmi.repository.URLRemoteRepository;
    Repository repository = new
URLRemoteRepository("http://localhost:8080/rmi");

BR,

Jukka Zitting