Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [riena-dev] Riena Logging

Stefan knows more about this and he can answer that question when he returns next week. I think when I look at the code in LoggerMill what happens is that if you have include equinox.log in your runtime, you will get an OSGi Service ExtendedLogReaderService.

If we find that service we try to register there any instance of the class in extension point org.eclipse.riena.core.logging.listeners. That listener must be a org.osgi.service.log.LogListener. If there is no extension we have a fallback strategy to then register the SysoLogListener......

So maybe you could write a LogListener that feeds the log entries into slf4j and that would work for you.

christian
Am 18.09.2008 um 16:06 schrieb ekkehard:

hi christian,

I opened bugzilla 247680 (duplicate log entries).
perhaps someone can explain in detail the logging concepts of riena ?
perhaps in riena wiki ?

I commented in SysoLogListener the lines
//        System.out.println(buffer.toString());
//        if (eEntry.getException() != null) {
//            eEntry.getException().printStackTrace(System.out);
//        }
and now I'm getting only one log message from riena

then I commented in Log4jLogListener
//        if (url != null) {
//            // workaround to fix class loader problems with log4j
//            // implementation. see "eclipse rich client platform, eclipse
//            // series, page 340.
//            Thread thread = Thread.currentThread();
//            ClassLoader loader = thread.getContextClassLoader();
//            thread.setContextClassLoader(this.getClass().getClassLoader());
//            try {
//                // configure the log4j with given config
//                DOMConfigurator.configure(url);
//            } finally {
//                thread.setContextClassLoader(loader);
//            }
//        } else {
//            // TODO: handle this ...
//        }
and removed org.log4j.xml from import and from MANIFEST.MF dependencies

then I could replace the standard org.apache.log4j bundle
by log4j-over-slf4j :-)

now I'm able to use ONE log implementation (logback as native slf4j implementation)
and can configure in my logback.xml logging for all used bundles, per ex.
Riena (thru log4j-over-slf4j)
EasyBeans (java.util.logging-to-slf4j)
Hibernate (slf4j)
jbpm (common-logging over slf4j)
etc

of course I dont know if my commented code above will have side-effects
and I still dont know where the other DEBUG-log-line of riena comes from
and if there's a place to configure this

perhaps I can get some info ?
...just working on a blog about this logging
and also worjking on a sample server combining riena + easybeans / hibernate

THX

ekke


Christian Campo schrieb:
Sounds strange......I briefly looked into the code, but I think someone else can make better sense of it, when he returns next to the office.

Duplicate errorlog entries  look like a bug, so please open a bugzilla entry.....

christian

--

ekkehard gentz
software-architect
erp-consultant
max-josefs-platz 30, D-83022 rosenheim, germany
homeoffice (1+1 VoIP): +49 8031 2068 325
mobile (iPhone): +49 151 19424929
mailto:ekkehard@xxxxxxxxxxxxxxxxx
homepage: http://www.gentz-software.de
opensource: http://ekkehard.org
blog (en): http://ekkes-corner.org
blog (de): http://ekkes-ecke.org
skype: ekke.gentz
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490

_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev


Back to the top