[
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249252#comment-15249252
]
Antonio Sanso commented on SLING-5638:
--
documented limitation in r1739790
> Sling:al
[
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-5638.
--
Resolution: Fixed
Fix Version/s: Resource Resolver 1.5.0
> Sling:alias property not worki
+1 Approve the release
Chetan Mehrotra
On Thursday 14 April 2016 13:47:40 Julian Sedding wrote:
> Hi,
>
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12328732
+1
O.
[
https://issues.apache.org/jira/browse/SLING-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-4464.
-
Resolution: Done
[r1739998|https://svn.apache.org/r1739998]
[r173|https://svn.apache.org/r1739
[
https://issues.apache.org/jira/browse/SLING-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-5655.
-
Resolution: Done
[r1738384|https://svn.apache.org/r1738384]
[r1738385|https://svn.apache.org/r1738
[
https://issues.apache.org/jira/browse/SLING-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-5663.
-
Resolution: Done
[r1739985|https://svn.apache.org/r1739985]
> Make Thymeleaf TemplateEngine avail
[
https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5579.
Resolution: Invalid
> setActive is not set to true during activation of
> CommonResourceRes
[
https://issues.apache.org/jira/browse/SLING-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248178#comment-15248178
]
Konrad Windszus commented on SLING-1421:
Does proposal SLING-5672 sound like a via
[
https://issues.apache.org/jira/browse/SLING-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5672:
---
Description:
Currently if any wildcards are used in the regular expressions for the Root
Mapp
Again my answers are inline.
> On 19 Apr 2016, at 16:42, Julian Sedding wrote:
>
> Hi Konrad
>
> See my reply inline.
>
> Regards
> Julian
>
> On Tue, Apr 19, 2016 at 3:32 PM, Konrad Windszus wrote:
>> Hi Julian,
>> thanks for that hint. I will try it out.
>> Still it is not possible with b)
Konrad Windszus created SLING-5672:
--
Summary: Allow wildcards within hostname, port and scheme to be
used and still use the entry for reverse mapping
Key: SLING-5672
URL: https://issues.apache.org/jira/browse/SLI
[
https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5671:
---
Summary: Not matching port in the mapping entry still leads to using this
entry for the outwar
I added documentation about SLING-2560 in https://svn.apache.org/r1739954.
Please quickly cross-check
http://sling.staging.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html,
afterwards I will publish the changes.
Thanks,
Konrad
> On 19 Apr 2016, at 15:12, Julian Sed
Hi Konrad
See my reply inline.
Regards
Julian
On Tue, Apr 19, 2016 at 3:32 PM, Konrad Windszus wrote:
> Hi Julian,
> thanks for that hint. I will try it out.
> Still it is not possible with b) to have the same mapping rule being applied
> to all hosts/schemes/ports without maintaining it separ
Konrad Windszus created SLING-5671:
--
Summary: Not matching port in the mapping entry still uses the
mapping for the outward mapping (used in ResourceResolver.map)
Key: SLING-5671
URL: https://issues.apache.org/ji
[
https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5671:
---
Description:
The following resource structure:
{code}
/etc/map
+ http
+ localhost:80
[
https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5671:
---
Description:
The following resource structure:
{code}
/etc/map
+ http
+ localhost:80
[
https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5671:
---
Description:
The following resource structure:
{code}
/etc/map
+ http
+ localhost:80
[
https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5671:
---
Description:
The following resource structure:
{code}
/etc/map
+ http
+ localhost:80
I think approach b) has a couple of short comings for larger sites as well
a good example are bucket pages (say you have to bucket content because
otherwise you have to many subnodes). I've seen sites where these bucket
pages are removed from the urls.
a secondary issue is that the upstream
Hi Julian,
thanks for that hint. I will try it out.
Still it is not possible with b) to have the same mapping rule being applied to
all hosts/schemes/ports without maintaining it separately for each
host/scheme/port.
I very often use the vhost section in the web server in front to do the mapping
On Tue, Apr 19, 2016 at 3:12 PM, Julian Sedding wrote:
> ...The whole mapping business is overly complicated IMHO and any reduction
> of the complexity is welcome
Indeed. I would suggest that people who are actively managing large
Sling instances in the field (hint, hint ;-) come up with prop
Hi Konrad
In my opinion b) is the preferred way, even though it is slightly more
complicated to configure.
Use-case 1) is possible with b), but not very well documented.
Essentially, you can provide a regexp as the value of
sling:internalRedirect (and replacements in sling:match), in which
case t
Currently there are two possibilities to configure the resource resolver
mapping:
a) Through the OSGi property "resource.resolver.mapping" of the PID
org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl
b) Through the resources below the path being specified by the OSGI property
Konrad Windszus created SLING-5670:
--
Summary: The OSGi property "resource.resolver.mapping" does not
allow to restrict mapping to certain schemes or hosts
Key: SLING-5670
URL: https://issues.apache.org/jira/brows
Hi,
On Mon, Apr 18, 2016 at 4:20 PM, Timothée Maret
wrote:
> ...One aspect that may differentiate asset processing from general job use
> case is the guarantees offered from the job delivery. Some use case would
> be fine with "at-least-one" or "maybe" delivery whereas some use case will
> need "
Hi,
On Mon, Apr 18, 2016 at 4:04 PM, Ian Boston wrote:
> ...I am not certain how a Callable will work with a distributed
> implementation,...
Ok, what shape a batch job takes is not very important at this stage,
I get your point.
...
>> void registerBatchEventListener(BatchEventsListener bl
We're missing one binding vote. Anyone?
Regards
Julian
On Thu, Apr 14, 2016 at 3:33 PM, Daniel Klco wrote:
> +1
>
> On Thu, Apr 14, 2016 at 7:47 AM, Julian Sedding wrote:
>
>> Hi,
>>
>> We solved 3 issues in this release:
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12328732
>>
Hi,
We solved 4 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12334744
** New Feature
* [SLING-5459] - Recording of tracer logs
** Sub-task
* [SLING-5504] - Reduce memory footprint of stored recording data
* [SLING-5505] - Allow recording of caller
[
https://issues.apache.org/jira/browse/SLING-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-5459.
Resolution: Fixed
All planned work done
> Recording of tracer logs
> --
[
https://issues.apache.org/jira/browse/SLING-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247453#comment-15247453
]
Chetan Mehrotra commented on SLING-5459:
Opened SLING-5669 to track that
> Record
[
https://issues.apache.org/jira/browse/SLING-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-5507.
Resolution: Fixed
> Collect more details around query execution
> --
[
https://issues.apache.org/jira/browse/SLING-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-5669:
---
Description:
In SLING-5459 [~bdelacretaz] suggested that Tracer should provide a way to
secur
[
https://issues.apache.org/jira/browse/SLING-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-5669:
---
Fix Version/s: (was: Log Tracer 1.0.0)
Log Tracer 1.0.2
> Restrict usag
Chetan Mehrotra created SLING-5669:
--
Summary: Restrict usage of log tracing feature with access control
Key: SLING-5669
URL: https://issues.apache.org/jira/browse/SLING-5669
Project: Sling
I
36 matches
Mail list logo
