[Exist-open] default-permissions in trunk/triggers?

[Efraim F. <efr...@gm...>]

Hi all,

I think I figured out the source of the exception I've been seeing (the 
latest 1.5 trunk) in my recent report 
<http://exist.2174344.n4.nabble.com/Exception-in-xmldb-store-with-trigger-in-recent-trunk-tp3705217p3705217.html>:

(1) I'm getting "org.exist.xquery.XPathException: permission to remove 
document denied" on attempting to update.
I think that in the exception thrown on line 147 of 
src/org/exist/xquery/update/Insert.java, the error message should 
probably be "permission to update document denied."

(2) In the new permissions model, for an XML file is the u permission 
still supposed to be an update permission, or is it an execute 
permission (essentially a no-op) and the write permission the same as 
update?

If the u permission is a no-op, I should not be getting this error 
message on a resource with 644 permissions where my running user is the 
owner. If it is not, I would need some way to make the permissions at 
least 744 before the create trigger runs.

(3) The obvious way to do (2) is the default-permissions element in 
conf.xml. As far as I can tell, setting the resource parameter to 770 is 
doing nothing.

Thank you,

-- 
---
Efraim Feinstein
Lead Developer
Open Siddur Project
http://opensiddur.net
http://wiki.jewishliturgy.org