[MAGNOLIA-1685] UUIDLink gets incorrect repository using URI2Repository mappings Created: 16/Aug/07  Updated: 23/Jan/13  Resolved: 21/Aug/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: Tom Jensen Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 5m
Time Spent: Not Specified
Original Estimate: 5m
Environment:

N/A


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
Date of First Response:

 Description   

Line 108:

repository = URI2RepositoryManager.getInstance().getRepository(handle);

Should pass in the link variable and not the handle. The reason being that the handle is stripped of any possible URI prefix that is mapped under /server/URI2RepositoryMapping so when the getRepository() method is called it is looking for a repository mapping on a string that already had its URI prefix for repository mapping removed. Because of that the UUIDLink that is generated will always point to the website repository.



 Comments   
Comment by Philipp Bracher [ 21/Aug/07 ]

Committed.

Thanks!

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