No, the "osgi:" stuff is how pax logging will recognize a pax appender and will look for the appender in the OSGi registry. Spring is irrelevant here, it's just how we register the pax appender in the OSGi registry. See https://scm.ops4j.org/repos/ops4j/qa/pax/pax-logging-1.1.1/service/src/main/java/org/apache/log4j/PaxLoggingConfigurator.java
On Fri, Sep 26, 2008 at 11:36 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Fri, Sep 26, 2008 at 5:19 PM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> We've written one in ServiceMix and have found no problem with it. >> The appender is exported in the OSGi registry using spring and the >> following beans: > > Thanks for the heads-up. Now when you mention it, I think I recall > some patches made by you at the time. > >> log4j.rootLogger=INFO, out, osgi:VmLogAppender >> >> So in short, the appender must be registered in the OSGi registry >> using the org.ops4j.pax.logging.spi.PaxAppender interface and have a >> service property named org.ops4j.pax.logging.appender.name. The value >> of this property can be referenced using osgi:[value]. > > So, the "osgi:" is something that is Spring-DM specific, IIUIC. > > Cheers > Niclas > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://open.iona.com _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
