<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CQ5 on ilikeorangutans</title><link>https://kuelzer.ca/tags/cq5/</link><description>Recent content in CQ5 on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:00:22 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/cq5/index.xml" rel="self" type="application/rss+xml"/><item><title>Apache Sling Resource Resolver Rules in a Nutshell</title><link>https://kuelzer.ca/posts/2012/11/20/apache-sling-resource-resolver-rule-priority-explained/</link><pubDate>Tue, 20 Nov 2012 13:59:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2012/11/20/apache-sling-resource-resolver-rule-priority-explained/</guid><description>&lt;p&gt;If you work with Apache Sling, you have probably encountered the ResourceResolver and its configuration rules.
In short, the ResourceResolver is the part of Sling that resolves incoming requests to actual or virtual
resources. For example, if a request for &lt;code&gt;/foo/bar&lt;/code&gt; is coming in the resolver will resolve that to a
corresponding node in the JCR. However, sometimes it is not desireable to expose the internal structure of the
repository or the required external structure cannot be represented using the JCR. In that case the resolver
can be customized by installing resolver rules. Resolver rules can be modified via the OSGI configuration
editor or the OSGI ConfigurationAdmin.&lt;/p&gt;</description></item></channel></rss>