[MAGNOLIA-1388] Warning for unmapped repositories (ContentRepository.hasRepositoryMapping() does not work properly) Created: 17/Feb/07  Updated: 17/Feb/07  Resolved: 17/Feb/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: 3.1 M1

Type: Bug Priority: Minor
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When an acl is set on an unmapped repository (this typically happens with dms if the dms module is not installed) a WARN is traced in the log by ContentRepository.getRepositoryMapping():

WARN info.magnolia.cms.beans.config.ContentRepository ContentRepository.java(getRepositoryMapping:564) 17.02.2007 22:43:39 no mapping for the repository [dms]

this should not happen since the code in JCRAuthorizationModule does:

if (!ContentRepository.hasRepositoryMapping(repositoryName))

{ // may be: default users may have permissions for the workflow or dms repositories, but // if the optional modules are not installed no ACL should be set continue; }

workspaceName = ContentRepository.getDefaultWorkspace(name);

but ContentRepository.getDefaultWorkspace(name) does a different check than hasRepositoryMapping() in order to determine if a repository has been registered.



 Comments   
Comment by Fabrizio Giustina [ 17/Feb/07 ]

fixed in trunk

Generated at Mon Feb 12 03:26:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.