[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532653
]
Felix Meschberger commented on SLING-40:
----------------------------------------
Removed the old interfaces in the org.apache.sling.core.mapper package in Rev.
582247.
These interfaces were very outdated and dysfunctional. They are replaced by the
new o.a.s.core.ResolvedURL and o.a.s.core.ContentResovler interfaces.
> Define proper ContentResolver service
> -------------------------------------
>
> Key: SLING-40
> URL: https://issues.apache.org/jira/browse/SLING-40
> Project: Sling
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Mapping request URI paths to Content objects is currently implemented in the
> URLMapperFilter, which is registered as a request filter for Sling. Other
> than that this functionality is not currently usable.
> Instead the mapping functionality should be defined in a separate service,
> which we could name ContentResolver (just like the ComponentResolver which
> selects the component) . This service may be implemented by a specifialized
> class. That class might even provide for extensibility.
> The URLMapperFilter should be renamed to ContentResolverFilter to match the
> service name and would be refactored to use the ContentResolver service as
> available and log appropriate messges if missing. Actually, the filter could
> be the service itself, but it should be ensured, that the filter would be
> available even in the absence of a repository to provide meaningfull error
> handling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
