Hi.
Thanks for the answers. Is there any date scheduled for the upgrade to
Jackrabbit 1.5? ACL was what I was thinking to use, so maybe the upgrade
resolves my problem (although I haven't been able to find much documentation
on ACL in 1.5 (if someone knows where I can find it I'll appreciate the
Hi Felix.
I tested what you told me, but I've seen it's not going to be possible only
exporting org.apache.jackrabbit.core.security due to the fact that the
AccessManager interface uses org.apache.jackrabbit.core.ItemId (so it will
also need org.apache.jackrabbit.core exported, that by what you
Hi Sebastien,
Sebastian Gomez schrieb:
Hi.
Thanks for the answers. Is there any date scheduled for the upgrade to
Jackrabbit 1.5? ACL was what I was thinking to use, so maybe the upgrade
resolves my problem (although I haven't been able to find much documentation
on ACL in 1.5 (if someone
On Wed, Dec 17, 2008 at 10:25 AM, Sebastian Gomez sage...@gmail.com wrote:
Is there any date scheduled for the upgrade to Jackrabbit 1.5?
See http://issues.apache.org/jira/browse/SLING-769
I think it will happen rather soon.
Regards,
Alex
--
Alexander Klimetschek
Hi Sebastien,
The main problem with exporting from the jackrabbit-core library is,
that the service provider API (or internal API) like PersistenceManager
or AccessManager is not properly separated from the actual
implementation. Therefore just exporting everything is unsuitable
because it leeks
You may also need org.apache.jackrabbit.spi.* if you use some
HierarchyManager methods (e.g. getPath) in your AccessManager. I added
the snippet below to jackrabbit-server bundle's POM:
Export-Package
org.apache.jackrabbit.core.*,
org.apache.jackrabbit.spi.*
/Export-Package
Sebastian
Hi everyone.
I'm trying to secure the JCR repository creating a custom LoginModule and
AccessManager. The first one has gone OK, as it implements the JAAS standard
interface. On the other hand, the second one must implement Jackrabbit's
AccessManager interface, but as Sling's Jackrabbit Embedded
Hi Sebastian
I went this route back in August, and came up against the same problems
(see [1]). I had the AccessManager working by exporting the .spi
classes from Sling's Jackrabbit bundle, but would intermittently run
into issues with the JAAS LoginModule after restarts. I think there may
On 17 Dec 2008, at 03:59, Rory Douglas wrote:
As for the AccessManager, I think there are plans to upgrade Sling
to Jackrabbit 1.5, so it may be more worthwhile to wait for that
use the repository-ACL-based AccessManager that comes with 1.5
rather than implementing your own. Or ping me
