[MAGNOLIA-3853] Refactor JCR Session creation/registration Created: 07/Oct/11  Updated: 19/Mar/12  Resolved: 10/Jan/12

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5

Type: Task Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-4253 Session acquisition: drop WorkspaceAc... Closed
is related to MAGNOLIA-4257 Content-API should just act as a facade Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   
  • drop WorkspaceAccessUtil as it is now
  • especially createAdminRepositorySession(), getCredentials() & getDefaultCredentials(): the later two should go to something like a CredentialUtil
  • split ContentRepository in WorkspaceMapping (Mappings), RepositoryLoader (intialization of repos) & ContentRepo (Constants)
  • add something like WorkspaceMapping#getLogicalWorkspaceName(session) as Session#getName() will only return physical workspace name that might not be unique
  • BaseSyndicatorImpl.REPOSITORY_NAME
    -> get rid of repository name
  • rename RepositoryAcquiringStrategy to JCRSessionStrategy


 Comments   
Comment by Daniel Lipp [ 21/Oct/11 ]

updated with results from coordination session

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