You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2022/02/04 09:16:00 UTC
[jira] [Created] (SLING-11120) Reduce log output from BundledScriptTracker
Carsten Ziegeler created SLING-11120:
----------------------------------------
Summary: Reduce log output from BundledScriptTracker
Key: SLING-11120
URL: https://issues.apache.org/jira/browse/SLING-11120
Project: Sling
Issue Type: Improvement
Components: Servlets
Reporter: Carsten Ziegeler
Fix For: Servlets Resolver 2.9.4
With bundled scripts it might happen that a lot of warnings are outputted, like below. It's usually a capability that doesn't provide its own script, nor does it have a main script or selector script in the one from which it inherits.
This can also happen if folders in libs hvae a sling:resourceSuperType on them without having scripts in the chain. Sometimes the reason for that is to trigger the Sling Resource Merger for a component dialog
As this warning does not really provide something actionable but just fills the logs, we should reduce the log level to Debug.
{noformat}
04.02.2022 09:30:43.427 *WARN* [FelixStartLevel] org.apache.sling.servlets.resolver.internal.bundle.BundledScriptTracker Unable to locate an executable for capability BundledRenderUnitCapability[sling.servlet.resourceTypes=[/libs/foo/templates/bar, foo/templates/bar]; extends=foo/myerviceconfigs/templates/configpage].
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)