[MAGNOLIA-3215] Encapsulate usage of JackRabbit specific API to parse paths Created: 26/May/10  Updated: 23/Jan/13  Resolved: 26/May/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.0.3
Fix Version/s: 4.3.2

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-2259 Handle special characters properly wh... Closed
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   

Wrap the usage of JR specific APIs so when using other repository implementations used does not need to keep JR jars around.

The reason for using implementation specific API is that JCR API doesn't have any methods to validate the path prior to attempt to use it and using incorrect path results in an error logged by the JackRabbit.


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