[MAGNOLIA-8225] Consider deprecating /server/URI2RepositoryMapping Created: 11/Nov/21  Updated: 05/Apr/22

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-8290 Repository mapping fails in combinati... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

This mapping allows to serve content

  • either mgnl:renderable (pretty much nothing except mgnl:page these days, used to be mgnl:resource)
  • jcr:data nodes (only contacts/personas in demo bundle)

from different workspaces.

The default configuration involves these mappings:

Relevant documentation:
https://docs.magnolia-cms.com/product-docs/6.2/Administration/URI-mapping/URI-to-repository-mapping.html
https://docs.magnolia-cms.com/product-docs/6.2/Administration/Architecture/Request-processing-and-filters/Filters.html#_repository_mapping
https://docs.magnolia-cms.com/product-docs/6.2/Features/Search/Jackrabbit-search.html#_configuring_uri2repository_mapping

Uri2Repository mapping can be still relevant in multisite context.

Configuration in the site definition overrides the configuration in /server/URI2RepositoryMapping/mappings/<workspace>, resulting in site-specific definitions.


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