[
https://issues.apache.org/jira/browse/FELIX-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239466#comment-14239466
]
Peter Kriens commented on FELIX-4720:
-------------------------------------
Surprised about the reactions. Fact is, it does not work ... You can blame
Equinox but that is not going to help anybody. I filed a bug with Equinox to or
disable or create a buffer but fact is they are compliant however you want to
interpret the spec.
If this was my project I would already have implemented :-) How hard can it be?
P.S. The Log Reader Service not a whiteboard ... I can honestly tell you that I
tried very hard to make it whiteboard but failed just before OSGi Release 1.
That loss also was the reason HttpService is not whiteboard. So don't blame me
... :-)
> Web Console and Gogo rely on Log history buffer in the Log Service
> ------------------------------------------------------------------
>
> Key: FELIX-4720
> URL: https://issues.apache.org/jira/browse/FELIX-4720
> Project: Felix
> Issue Type: Bug
> Components: Gogo Command, Web Console
> Reporter: Peter Kriens
>
> The OSGi Log Reader Service has a command to get the history of the log.
> However, the specification states that this history can be empty. The Equinox
> framework is nowadays registering a Log Reader Service that has such an empty
> history to prevent pinning objects in memory.
> Using the history this way was always at odds with the specification since
> the history was only intended to hold the start up events. The primary model
> of the Log Service is a dispatcher.
> I suggest that the Gogo log command and the Web Console maintain their own
> history buffer to become independent on this fragile history buffer in the
> Log Reader service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
