Re: Configuring Sling ResourceResolver
@Marty: shows what? How to enter rules? The docs are here: http://sling.apache.org/site/mappings-for-resource-resolution.html but they could be better. Also, the samples do not work as advertised. Creating a node with sling:match=http/localhost\.\d* results in the following rule: ^http/localhost.d*.80 Notice how the rules has a .80 attached to it, making it impossible to write rules that match any ports. Is this a bug? I couldn't find anything about this in JIRA, so I assume it might be new. On Fri, Nov 2, 2012 at 9:09 AM, Marty Phee wrote: > Do you have a link which shows this? > > > > On Nov 2, 2012, at 7:29 AM, Alexander Klimetschek > wrote: > > > On 01.11.2012, at 18:30, Jakob Külzer wrote: > >> What is the recommended way of configuring the resolver? Obviously, > having > >> someone enter the rules manually on the console is not an option, so > >> something that is stored in the tree and can be packaged and redeployed > >> would be ideal. Is there a way to configure the ResourceResolver (the > >> JcrResourceResolverImpl to be more precise) via sling:OsgiConfig? > > > > I think the best way is to configure them via /etc/map, this can be > packaged. > > > > Cheers, > > Alex > > > > > -- Cheers, Jakob
Re: Configuring Sling ResourceResolver
Do you have a link which shows this? On Nov 2, 2012, at 7:29 AM, Alexander Klimetschek wrote: > On 01.11.2012, at 18:30, Jakob Külzer wrote: >> What is the recommended way of configuring the resolver? Obviously, having >> someone enter the rules manually on the console is not an option, so >> something that is stored in the tree and can be packaged and redeployed >> would be ideal. Is there a way to configure the ResourceResolver (the >> JcrResourceResolverImpl to be more precise) via sling:OsgiConfig? > > I think the best way is to configure them via /etc/map, this can be packaged. > > Cheers, > Alex > >
Re: Configuring Sling ResourceResolver
On 01.11.2012, at 18:30, Jakob Külzer wrote: > What is the recommended way of configuring the resolver? Obviously, having > someone enter the rules manually on the console is not an option, so > something that is stored in the tree and can be packaged and redeployed > would be ideal. Is there a way to configure the ResourceResolver (the > JcrResourceResolverImpl to be more precise) via sling:OsgiConfig? I think the best way is to configure them via /etc/map, this can be packaged. Cheers, Alex
Configuring Sling ResourceResolver
Hey guys, we're implementing Sling ResourceResolver rules on DayCQ 5.5, but I'm unsure how to configure them other than with the console. Ideally we'd configure the resolver using the sling:OsgiConfig nodes, but after creating a node with the pid org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl, the changes are not picked up. I ended up digging into the source code of org.apache.sling.resource (deprecated, but that's what the config console says we're using) and then org.apache.sling.resourceresolver package, but I'm not quite sure what to make of it, and I figured it would be easier to ask ;) I've started reading http://sling.apache.org/site/mappings-for-resource-resolution.html which seems to be the appropriate way of implementing rules, but I wonder how it relates to the rules entered in the console (under localhost:4502/system/console/configMgr). What is the recommended way of configuring the resolver? Obviously, having someone enter the rules manually on the console is not an option, so something that is stored in the tree and can be packaged and redeployed would be ideal. Is there a way to configure the ResourceResolver (the JcrResourceResolverImpl to be more precise) via sling:OsgiConfig? Thanks so much for any help. -- Cheers, Jakob
