[
https://issues.apache.org/jira/browse/SLING-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4563:
-----------------------------------------
Attachment: SLING-4563.patch
Attached patch for LogSupport: [^SLING-4563.patch]
Requires org.osgi 4.3.0 since that added the FrameworkStartLevel class, the old
(deprecated) approach of the StartLevel service is difficult in the LogSupport
class, since it would need to reference the service (it doesn't have any
service references so far).
The simple string concatenation should be ok, a startlevel changed event is
extremely rare.
> Log start level number on STARTLEVEL CHANGED event
> --------------------------------------------------
>
> Key: SLING-4563
> URL: https://issues.apache.org/jira/browse/SLING-4563
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Alexander Klimetschek
> Attachments: SLING-4563.patch
>
>
> Currently, the Sling logservice just logs that an osgi start level has
> changed, without indicating which one:
> {noformat}
> ...org.apache.felix.framework FrameworkEvent STARTLEVEL CHANGED
> {noformat}
> This should include the current framework startlevel:
> {noformat}
> ...org.apache.felix.framework FrameworkEvent STARTLEVEL CHANGED to 14
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
