Richard S. Hall wrote:
John E. Conlon wrote:
3. Many application libraries dynamically import APIs, that might not
actually be available, and catch and ignore the exception if classes are
not available via the classloader. Libraries that relie on the
JavaBeans model do this. Failure to find a class is not considered a bad
thing for these libraries. Felix considers failure to load classes an
event worthy of a log message at the WARN level.
WARNING: *** Class 'java.lang.ObjectBeanInfo' was not found. Bundle 23
does not import package 'java.lang', nor is the package exported by any
other bundle or available from the system class loader. ***
(java.lang.ClassNotFoundException: *** Class 'java.lang.ObjectBeanInfo'
was not found. Bundle 23 does not import package 'java.lang', nor is the
package exported by any other bundle or available from the system class
loader. ***)
In applications using libraries utilizing these techniques the user is
often overwhelmed with WARN framework messages which can obscure events
that require user attention. This problem is made all the more
problematic when Felix uses a LogService that outputs stacktraces for
exceptions.
Should we downgrade Felix classloading events a lower loglevel?
We could make them "debug" messages, I suppose. I am not against it.
Does any one else have any feeling about this one?
-> richard
