[
https://issues.apache.org/jira/browse/SLING-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011740#comment-16011740
]
Chetan Mehrotra commented on SLING-6482:
----------------------------------------
Missed looking into this. Yes the logic related to empty path and treating that
as console is not clean. This was done to support some backward compatibility
requirement for Sling Log 3.x version. Would try to look into this and
SLING-6577 but given current backlog this may take some time (hopefully next
week)
> Commons Log WebConsole: Exception when creating logger with an empty log file
> -----------------------------------------------------------------------------
>
> Key: SLING-6482
> URL: https://issues.apache.org/jira/browse/SLING-6482
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Log 5.0.0
> Reporter: Bjoern Weide
> Priority: Minor
> Fix For: Commons Log 5.0.2
>
> Attachments: SLING-6482-v01.patch
>
>
> When creating a new logger via WebConsole specifying an empty logfile it
> causes an StringIndexOutOfBoundsException when (re-)opening the WebConsole.
> {noformat}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1931)
> at
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.getPath(SlingLogPanel.java:791)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
