I've been reading posts about implementing an AccessManager that stores
access information as node properties. The solution I've seen is to use
a systemSession to access this node properties. Now, I'm programming my
own AccessManager with this approach and there is an bug reported in
you can't :-)
regards, toby
On 8/1/06, Paco Avila [EMAIL PROTECTED] wrote:
I've been reading posts about implementing an AccessManager that stores
access information as node properties. The solution I've seen is to use
a systemSession to access this node properties. Now, I'm programming my
own
Hi,
On 7/31/06, Julian Reschke [EMAIL PROTECTED] wrote:
attached is a set of patches to reduce the number of JavaDoc warnings (I
guess we don't want to open an issue for that, right? :-).
Thanks! Committed as related to the javadoc issue JCR-73.
In general I would prefer to process all
Jukka Zitting schrieb:
Thanks! Committed as related to the javadoc issue JCR-73.
Thanks.
In general I would prefer to process all patches through Jira for
better tracking of changes and contributions.
Ok. In this particular case, does it make sense to open a new JIRA issue
for each
And now which possibilites do I have? Is possible to implement an custom
AccessManager actually?
El mar, 01-08-2006 a las 11:20 +0200, Tobias Bocanegra escribió:
you can't :-)
regards, toby
On 8/1/06, Paco Avila [EMAIL PROTECTED] wrote:
I've been reading posts about implementing an
Hi,
On 8/1/06, Paco Avila [EMAIL PROTECTED] wrote:
And now which possibilites do I have? Is possible to implement an custom
AccessManager actually?
I suppose your problem is caused by Jackrabbit asking for permissions
on a node that hasn't yet been persisted, so you can't access it from
your
[ http://issues.apache.org/jira/browse/JCR-332?page=all ]
Christoph Kiehl updated JCR-332:
Attachment: pom.xml.patch
Added a patch which does the following:
- Change artifactId from jackrabbit to jackrabbit-core
- Omit generating XPath.jjt
- Use
[
http://issues.apache.org/jira/browse/JCR-332?page=comments#action_12424821 ]
Jukka Zitting commented on JCR-332:
---
Thanks for the update! Committed in revision 427531.
maven2 pom contribution
---
Key:
El mar, 01-08-2006 a las 13:17 +0300, Jukka Zitting escribió:
Hi,
On 8/1/06, Paco Avila [EMAIL PROTECTED] wrote:
And now which possibilites do I have? Is possible to implement an custom
AccessManager actually?
I suppose your problem is caused by Jackrabbit asking for permissions
on a
Hello,
I recently commented on JCR 153 that I have some time to contribute
towards implementing node level access control. I also noticed that
JCR 350 seems to be part of the same issue.
I was wondering if someone could show me how I should get started
with this. Are there other
El mar, 01-08-2006 a las 13:51 -0500, Michael Bletzinger escribió:
Hello,
I recently commented on JCR 153 that I have some time to contribute
towards implementing node level access control. I also noticed that
JCR 350 seems to be part of the same issue.
I was wondering if someone
11 matches
Mail list logo
