Re: [DISCUSS] Automatic Mapping of URIs in HTL

Thanks, Georg! I’ll try to have a look this week. Regards, Radu > On 23 Sep 2020, at 10:58, Georg Henzler wrote: > > I created issue SLING-9762 [1] for this. > > -Georg > > [1] https://issues.apache.org/jira/browse/SLING-9762 > > On 2020-09-11 16:55, Georg Henzler wrote: >> Hi Paul >>> The r

Re: [DISCUSS] Automatic Mapping of URIs in HTL

I created issue SLING-9762 [1] for this. -Georg [1] https://issues.apache.org/jira/browse/SLING-9762 On 2020-09-11 16:55, Georg Henzler wrote: Hi Paul The reason I think both the global config and the local config are necessary good point, +1 (both "global on/disable for one uri locally" a

Re: [DISCUSS] Automatic Mapping of URIs in HTL

Hi Paul The reason I think both the global config and the local config are necessary good point, +1 (both "global on/disable for one uri locally" and "global off/enable for one uri locally" are valid use cases) .. JSON or some JS objects in HTL scripts (thinking on how many times I had to go

Re: [DISCUSS] Automatic Mapping of URIs in HTL

I like your idea of hooking into the existing URI context processing, especially because you would want to have the mapping occur after URL manipulation (I think). My thoughts based on what has been said above: 1. Hook into the existing URI context, and implement the processing wherever URIs are p

Re: [DISCUSS] Automatic Mapping of URIs in HTL

Hi Radu, 1. Per URI as mentioned in template: This could work - it would be a Sling-specific option and we’ve done this in the past in https://issues.apache.org/jira/browse/SLING-5812 . The option would introduce a new runtime call to the ne

Re: [DISCUSS] Automatic Mapping of URIs in HTL

+1 for a dedicated option. Not sure about the naming though. Konrad > Am 11.09.2020 um 14:07 schrieb Radu Cotescu : > > Hi Georg, > >> On 11 Sep 2020, at 01:09, Georg Henzler wrote: >> >> Hi all, >> >> as briefly mentioned in the thread about the resource >> mapping SPI [1], it would be real

Re: [DISCUSS] Automatic Mapping of URIs in HTL

Hi Georg, > On 11 Sep 2020, at 01:09, Georg Henzler wrote: > > Hi all, > > as briefly mentioned in the thread about the resource > mapping SPI [1], it would be really useful if HTL > could auto-map URIs (regardless of the SPI) > - that way many projects that use the rewriting > pipeline [2] tod

Re: [DISCUSS] Automatic Mapping of URIs in HTL

Hi Nicolas, yes that makes sense, although maybe a bit overkill for one boolean flag it's conceptually cleaner than OSGi config with regex (no 3). Overall the question will be if this needs to be controlled per content root path or rather per (super)resourceType... Output Rewriting Pipelines allo

Re: [DISCUSS] Automatic Mapping of URIs in HTL

i like the idea! what about a context aware configuration? Le ven. 11 sept. 2020 à 01:09, Georg Henzler a écrit : > Hi all, > > as briefly mentioned in the thread about the resource > mapping SPI [1], it would be really useful if HTL > could auto-map URIs (regardless of the SPI) > - that way man

[DISCUSS] Automatic Mapping of URIs in HTL

Hi all, as briefly mentioned in the thread about the resource mapping SPI [1], it would be really useful if HTL could auto-map URIs (regardless of the SPI) - that way many projects that use the rewriting pipeline [2] today for that purpose could simplify their setup (and make it more performant).