Thanks.
Doesn't look like the LogService uses the jdk logger. So I don't see
too many options at this point.
Should the filter go in or do we live with the messages that we
currently have and come up with a more permanent solution in the next
release?
Carla
Major Péter wrote:
> Hi,
>
> LogService is just an interface, the implementation is here:
> http://apache.mirrors.crysys.hit.bme.hu/dist/felix/org.apache.felix.log-1.0.0-project.tar.gz
> -> org.apache.felix.log.LogServiceImpl
>
> Peter
>
> 2009-11-10 03:26 keltezéssel, Carla Mott írta:
>> Hi,
>>
>> If a logger is used I can't seem to get the logger name since the log
>> record returns 'null' for messages coming from fileinstall. Not sure
>> why I'm getting 'null'. Usually I can set the logger level in the
>> logging.properties file using the logger name.
>>
>> Where is the code for LogService?
>>
>> Carla
>>
>> Major Péter wrote:
>>>> Does it use log levels that we can influence or does it use println?
>>> It uses org.osgi.service.log.LogService if there is no problem while
>>> initializing logsystem. It uses StdOutLogger only if
>>>
>>> try {
>>> getClass().getClassLoader().loadClass(LogService.class.getName());
>>> } catch (ClassNotFoundException e) {
>>> throw new NoClassDefFoundError(e.getMessage());
>>> }
>>>
>>> couldn't run flawlessly. You can read the whole code in
>>> http://xenia.sote.hu/ftp/mirrors/www.apache.org/felix/org.apache.felix.fileinstall-2.0.4-project.tar.gz
>>>
>>> -> org.apache.felix.fileinstall.internal.Util . :)
>>>
>>> Regards,
>>> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>