Hello,
I am currently adapting the JeCARS custom accessmanager for Jackrabbit v1.5.
There is a "strange" thing I encounter while developing.
I see that when a new JCR object is created, before it is actually created
an READ permission is asked of the jcr:created property.
Because I override the i
hi jacco
I see that when a new JCR object is created, before it is actually created
an READ permission is asked of the jcr:created property.
in the item manager there is always a check for READ permission
on the id/path before the corresponding jcr item is created (or returned).
but the jcr:c
Hello Angela,
I've tried it.
I perform an addNode() and my own accessmanager the isGranted() method is
override'd and performs the following code;
String perm = null;
NodeId nodeId = mHierMgr.resolveNodePath( pPath );
PropertyId propId = null;
i
hi jacco
i see... the property is accessed during the creation of the
autocreated properties that's why.
let me take a closer look at this next week.
kind regards
angela
hi jacco
let me take a closer look at this next week.
... at a first glance, i assume that there is a bug in
NodeImpl: the corresponding call creating a new child
node does in fact use a diffent way to access the item.
that's probably wrong with createChildProperty.
i'll verify it (still next
Hello Angela,
Okay should I make a JIRA entry?
Gr.
Jacco
On Fri, Jan 16, 2009 at 5:28 PM, Angela Schreiber wrote:
> hi jacco
>
> let me take a closer look at this next week.
>>
>
> ... at a first glance, i assume that there is a bug in
> NodeImpl: the corresponding call creating a ne
hi jacco
Okay should I make a JIRA entry?
that would be nice. thanks otherwise
i would have created one ;)
angela
Hallo,
I need help on this Jackrabbit AccessManager.
I have custome AccessManager, providing access security based on the logged
account and the permissions an account has. Basically, the permissions apply
over a folder (kind of) - one can see a folder, put some items in it, edit
these items, et
hi ivo
I need help on this Jackrabbit AccessManager.
I have custome AccessManager, providing access security based on the logged
account and the permissions an account has. Basically, the permissions apply
over a folder (kind of) - one can see a folder, put some items in it, edit
these items, et
Hallo, Angela,
Thanks for spending time on my issue.
As I described in my previous post, to evaluate the permissions to be
granted to a session, I'm using impersonation. Thus, I'm getting a new
session having full access, hence, able to see any item, interrogate its
attributes and return proper
hi ivo
Getting back to your suggestion, is the "super" session able to see
itemstate for item, which is not yet persisted and is actually "owned" by
the session subject of authorization?
no... that's why i said that "you need to operate on the itemstate
level instead, if you want to retrieve c
11 matches
Mail list logo
