You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2022/09/30 11:11:00 UTC

[jira] [Comment Edited] (SLING-11602) Broken logging in vanity resolution

    [ https://issues.apache.org/jira/browse/SLING-11602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611516#comment-17611516 ] 

Robert Munteanu edited comment on SLING-11602 at 9/30/22 11:10 AM:
-------------------------------------------------------------------

Looks like the vanity path (String) is the result to a {{toString}} call on a string array.


was (Author: rombert):
Looks like the vanity path (String) is the result to a `toString` calls on a string array.

> Broken logging in vanity resolution
> -----------------------------------
>
>                 Key: SLING-11602
>                 URL: https://issues.apache.org/jira/browse/SLING-11602
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.9.0
>            Reporter: Joerg Hoh
>            Priority: Minor
>
> When trying the new feature of executing the vanity loading in the background, I found broken logging:
> {noformat}
> 28.09.2022 15:50:30.069 *WARN* [VanityPathInitializer] org.apache.sling.resourceresolver.impl.mapping.MapEntries Removing extension from vanity path sw.js
> 28.09.2022 15:50:30.275 *WARN* [VanityPathInitializer] org.apache.sling.resourceresolver.impl.mapping.MapEntries Removing extension from vanity path [Ljava.lang.String;@602f69d0
> {noformat}
> Sometimes it seems to work, sometimes not. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)