[jira] [Updated] (SLING-12054) WARN of the non-use of optimizedAliasResolution
[ https://issues.apache.org/jira/browse/SLING-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh updated SLING-12054: -- Description: As we found in SLING-12025, disabling the optimizedAliasResolution changes the behavior of the mapping result. This can be clearly considered a bug, but as it is part of the ResourceResolver for quite some time (although not default), we cannot fix or remove it that easily. We should write a WARN message into the log, when the optimizedAliasResolution is *NOT* used. The wording in the configuration (as shown in the OSGI Webconsole) should be adjusted too. The removal of this code path should be considered as next step, taking place in 12+ months earliest. was: As we found in SLING-12025, disabling the optimizedAliasResolution changes the behavior of the mapping result. This can be clearly considered a bug, but as it is part of the ResourceResolver for quite some time (although not default), we cannot fix or remove it that easily. We should write a WARN message into the log, when the optimizedAliasResolution is *NOT* used. The wording in the webconsole should be adjusted too. The removal of this code path should be considered as next step, taking place in 12+ months earliest. > WARN of the non-use of optimizedAliasResolution > > > Key: SLING-12054 > URL: https://issues.apache.org/jira/browse/SLING-12054 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Affects Versions: Resource Resolver 1.11.0 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Resource Resolver 1.11.2 > > > As we found in SLING-12025, disabling the optimizedAliasResolution changes > the behavior of the mapping result. This can be clearly considered a bug, but > as it is part of the ResourceResolver for quite some time (although not > default), we cannot fix or remove it that easily. > We should write a WARN message into the log, when the > optimizedAliasResolution is *NOT* used. The wording in the configuration (as > shown in the OSGI Webconsole) should be adjusted too. > The removal of this code path should be considered as next step, taking place > in 12+ months earliest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12054) WARN of the non-use of optimizedAliasResolution
[ https://issues.apache.org/jira/browse/SLING-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh updated SLING-12054: -- Description: As we found in SLING-12025, disabling the optimizedAliasResolution changes the behavior of the mapping result. This can be clearly considered a bug, but as it is part of the ResourceResolver for quite some time (although not default), we cannot fix or remove it that easily. We should write a WARN message into the log, when the optimizedAliasResolution is *NOT* used. The wording in the webconsole should be adjusted too. The removal of this code path should be considered as next step, taking place in 12+ months earliest. was: As we found in SLING-12025, disabling the optimizedAliasResolution changes the behavior of the mapping result. This can be clearly considered a bug, but as it is part of the ResourceResolver for quite some time (although not default), we cannot fix or remove it that easily. We should write a WARN message into the log, when the optimizedAliasResolution is *NOT* used. The wording in the webconsole just be adjusted too. The removal of this code path should be considered as next step, taking place in 12+ months earliest. > WARN of the non-use of optimizedAliasResolution > > > Key: SLING-12054 > URL: https://issues.apache.org/jira/browse/SLING-12054 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Affects Versions: Resource Resolver 1.11.0 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Resource Resolver 1.11.2 > > > As we found in SLING-12025, disabling the optimizedAliasResolution changes > the behavior of the mapping result. This can be clearly considered a bug, but > as it is part of the ResourceResolver for quite some time (although not > default), we cannot fix or remove it that easily. > We should write a WARN message into the log, when the > optimizedAliasResolution is *NOT* used. The wording in the webconsole should > be adjusted too. > The removal of this code path should be considered as next step, taking place > in 12+ months earliest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12054) WARN of the non-use of optimizedAliasResolution
[ https://issues.apache.org/jira/browse/SLING-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh updated SLING-12054: -- Fix Version/s: Resource Resolver 1.11.2 > WARN of the non-use of optimizedAliasResolution > > > Key: SLING-12054 > URL: https://issues.apache.org/jira/browse/SLING-12054 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Affects Versions: Resource Resolver 1.11.0 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Resource Resolver 1.11.2 > > > As we found in SLING-12025, disabling the optimizedAliasResolution changes > the behavior of the mapping result. This can be clearly considered a bug, but > as it is part of the ResourceResolver for quite some time (although not > default), we cannot fix or remove it that easily. > We should write a WARN message into the log, when the > optimizedAliasResolution is *NOT* used. The wording in the webconsole just be > adjusted too. > The removal of this code path should be considered as next step, taking place > in 12+ months earliest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12054) WARN of the non-use of optimizedAliasResolution
[ https://issues.apache.org/jira/browse/SLING-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh updated SLING-12054: -- Summary: WARN of the non-use of optimizedAliasResolution (was: Deprecate the non-use of optimizedAliasResolution ) > WARN of the non-use of optimizedAliasResolution > > > Key: SLING-12054 > URL: https://issues.apache.org/jira/browse/SLING-12054 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Affects Versions: Resource Resolver 1.11.0 >Reporter: Joerg Hoh >Priority: Major > > As we found in SLING-12025, disabling the optimizedAliasResolution changes > the behavior of the mapping result. This can be clearly considered a bug, but > as it is part of the ResourceResolver for quite some time (although not > default), we cannot fix or remove it that easily. > We should write a WARN message into the log, when the > optimizedAliasResolution is *NOT* used. The wording in the webconsole just be > adjusted too. > The removal of this code path should be considered as next step, taking place > in 12+ months earliest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
