timp/atombeat

security-protocol:do-get($request). XPDY0002 : variable '$CONSTANT:OP-RETRIEVE-COLLECTION-ACL' is not set

Closed this issue · 2 comments

What steps will reproduce the problem?
1. go to the atombeat collection admin page
2. create the collections
3. click on the /foo collection

What is the expected output? What do you see instead?
expect to see a normal feed, instead get error trace:

org.exist.xquery.XPathException
Error while evaluating expression: import module namespace security-protocol = 
'http://purl.org/atombeat/xquery/security-protocol' at 'security-protocol.xqm' 
; import module namespace config = 'http://purl.org/atombeat/xquery/config' at 
'../config/shared.xqm' ; let $login := xmldb:login( '/' , $config:exist-user , 
$config:exist-password ) return security-protocol:do-get($request). XPDY0002 : 
variable '$CONSTANT:OP-RETRIEVE-COLLECTION-ACL' is not set. [at line 185, 
column 12]
In call to function:
    security-protocol:do-get(element()) [1:314]
    plugin-util:security-protocol-do-get(element()) [350:30]
    link-expansion-plugin:expand-security-link(element(), element()) [218:83]
    link-expansion-plugin:expand-links(element()*, xs:string*, element()) [157:13]
    link-expansion-plugin:augment-feed(element(), element()) [121:32]
    link-expansion-plugin:after(xs:string, element(), element()) [38:17]
    common-protocol:apply-after(function*, xs:string, element(), element()) [416:21]
    common-protocol:apply-after(function*, xs:string, element(), element()) [416:21]
    common-protocol:apply-after(function*, xs:string, element(), element()) [416:21]
    common-protocol:apply-after(function*, xs:string, element(), element()) [416:21]
    common-protocol:apply-after(function*, xs:string, element(), element()) [300:46]
    common-protocol:apply-op(xs:string, function, element(), item()*) [1299:16]
    atom-protocol:do-get-collection(element()) [1093:9]
    atom-protocol:do-get(element()) [66:9]
    atom-protocol:do-service(element()) [36:22]
    atom-protocol:main() [14:26]

Original issue reported on code.google.com by alimanfoo@googlemail.com on 1 Mar 2011 at 9:07

looks like this is due to configuration of the link extensions plugin to expand 
the security-descriptor link in the feed context

Original comment by alimanfoo@googlemail.com on 1 Mar 2011 at 9:09

fixed in revision 628 by setting cache-flag to false on eval in plugin-util; 
was concerned this would affect performance, but doesn't seem to impact 
visibly, could do with some benchmarking tho

Original comment by alimanfoo@googlemail.com on 1 Mar 2011 at 10:28

  • Changed state: Fixed