I am not sure if it is a managed service or not, but probably not since
it is just a simple implementation. Implementing that in an optional way
might not be a bad idea, though...
However, for now I can think of a way, but it is sort of ugly. Since
bundle context properties are backed by system properties, I think you
could set the log configuration properties as system properties, but if
the log service was already active, you'd need to stop it and restart it
for the changes to take effect.
-> richard
On 10/12/09 18:54, Vlatko Davidovski wrote:
Hi!
I am using the Apache Felix LogService and would like to configure the
LogService, so that DEBUG messages are also stored in memory and to
increase the maximal size of the history.
On the page: http://felix.apache.org/site/apache-felix-log-service.html
there was this information listed:
org.apache.felix.log.maxSize 100 The maximum size of the log history.
org.apache.felix.log.storeDebug false Determines whether or not debug
messages will be stored in the history.
So I checked the services using:
inspect s c 5
Apache Felix Log Service (5) provides services:
-----------------------------------------------
objectClass = org.osgi.service.log.LogService
service.id = 25
----
objectClass = org.osgi.service.log.LogReaderService
service.id = 26
And seems that the LogService is not a ManagedService, no PID exposed.
How can I change these parameters in a programmatic way?
Regards,
Vlatko
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
