jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danner, Russ" <Dann...@csps.com>
Subject RE: Re: JackRabbit Vs Alfresco
Date Mon, 16 Apr 2007 23:40:30 GMT
Oh .. I wanted to mention that on the acegi issues you are correct
concerning the ThreadLocals. Executes in its own threads you aren't
gaurenteed to get the same thread on subsequent calls.  In reality that
doesn't matter because the Alfresc JCR implementation carries it's
security ticket and sets up the thread on each request.  However there
was a small bug in the code that was keeping this from happening.  


-----Original Message-----
From: Danner, Russ [mailto:DannerR@csps.com] 
Sent: Monday, April 16, 2007 7:36 PM
To: users@jackrabbit.apache.org
Subject: RE: Re: JackRabbit Vs Alfresco

As you point out the security is a problem, the other issue is
transactions.  Alfresco's underlying API is service based and is coarse
grained compaired to the JCR API so there are some challenges in mapping
the two IMO.  The security issues can be fixed with a patch.  We're
still looking at transactions.  


-----Original Message-----
From: Daniel Murley [mailto:dmurley@xbiosystems.com] 
Sent: Monday, April 16, 2007 7:34 PM
To: users@jackrabbit.apache.org
Subject: RE: Re: JackRabbit Vs Alfresco

The RMI layer for alfresco is somewhat poor, and virtually unusable if
you're not using Acegi for your security.

If you're not using Acegi for your security, you can expect to be able
execute 2 - 3 commands before it says you're unauthenticated (my guess
be because Acegi uses ThreadLocals, and RMI can be executed on different

The Jackrabbit RMI support is significantly better, and as such after
struggling with Acegi for 3-4 weeks, chucked it and had Jackrabbit doing
same thing in 2-3 days.


-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com] 
Sent: Sunday, 15 April 2007 6:17 PM
To: users@jackrabbit.apache.org
Subject: Re: Re: JackRabbit Vs Alfresco


On 4/15/07, Danner, Russ <DannerR@csps.com> wrote:
> Another important thing to note about the implementation is that
> currently the Alfresco JCR implementation has to run "in-process."

Note that the same applies to by default also to Jackrabbit. You can
use the jackrabbit-jcr-rmi remoting layer with any JCR implementation,
so it should work fine also with Alfresco.


Jukka Zitting

View raw message