Community
Participate
Working Groups
See bug 202278 for more details
I'll take it
Created attachment 82710 [details] org.eclipse.equinox.log.patch Here it is! I fixed up the log event adapter to be compliant with the spec, see section 101.6.4 for more details. In the old implementation, we weren't broadcasting events with the right topic. I also set the BREE to OSGi Minimum 1.1.
Created attachment 82711 [details] mylyn/context/zip
Tom to review.
Patch does not work. LogReader objects must be registered with the LogReaderService *not* the service registry. LogService (like HttpService) was developed before the white board pattern become popular in OSGi. I suggest you access the internal implementation of LogReaderService to add the LogEntryEventAdapter. This way you know you are only firing events for this implementation of the LogService not some other random one which may be installed.
That sucks, I love the whiteboard pattern. I guess you learn something new everyday.
Created attachment 82773 [details] org.eclipse.equinox.log.patch Ok, updated the patch to include the optional import and register the event adapter in the proper place.
Created attachment 84322 [details] patch The patch will not work properly unless a bundle is actually using the LogReaderService. This is because the LogEntryEventAdaptor is not registered as a LogListener until the LogReader factory creates a LogReader for a bundle. This patch instead makes the adaptor a LogListener and it is registered as a listener to the log impls LogReaderService. This will ensure that the log events are always propagated to EventAdmin even when no other LogListeners are registered with the LogReaderService.
Patch released for 3.4 M4.