[ 
https://issues.apache.org/jira/browse/SLING-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734019#action_12734019
 ] 

Marc commented on SLING-1047:
-----------------------------

Doesn't Sling-1028 (revision 790290) set PluggableDefaultAccessManager as 
default in the repository.xml? Hence the javadoc might be outdated. 

So I can't go back to default of repository.xml. While developing, it's also 
very inconvenient to edit it by hand after every fresh start.

You're right about the log.patch. It also does not take care of the log message 
from AccessManagerFactoryTracker. As I mentioned above, I'm not familiar this 
bundle, so the log.patch is more a pointer to the problem. 

> Using DefaultAccessManager fills up log
> ---------------------------------------
>
>                 Key: SLING-1047
>                 URL: https://issues.apache.org/jira/browse/SLING-1047
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: JCR Jackrabbit Server 2.0.5
>            Reporter: Marc
>            Priority: Trivial
>         Attachments: log.patch
>
>
> For security reasons, I deactivated the bundle 
> org.apache.sling.jcr.jackrabbit.accessmanager. This leads to several log 
> lines per repository access and makes reading the log unnecessarily 
> cumbersome. PluggableDefaultAccessManager is the culprit:
> 14.07.2009 17:46:17.903 *INFO* [127.0.0.1 [1247586206587] GET 
> /hugo/b/Usefull%20to%20know/ HTTP/1.1] 
> org.apache.sling.jcr.jackrabbit.server.impl.AccessManagerFactoryTracker 
> Registering PluggableDefaultAccessManager instance
> 14.07.2009 17:46:17.903 *WARN* [127.0.0.1 [1247586206587] GET 
> /hugo/b/Usefull%20to%20know/ HTTP/1.1] 
> org.apache.sling.jcr.jackrabbit.server.impl.security.PluggableDefaultAccessManager
>  No pluggable AccessManager available, falling back to DefaultAccessManager
> I'm not familiar with PluggableDefaultAccessManager nor the bundle, so the 
> patch might be more a problem indication than a solution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to