Re: Question about pax-logging-service

[David Leangen]

> What's this for, and why is it done this way rather than using BND?

There are some other funky things going on in the pax-logger code.

Here is the PaxLoggingConfigurator code:

public class PaxLoggingConfigurator extends PropertyConfigurator
{
    public static final String OSGI_APPENDER_PREFIX = "osgi:";

    private AppenderTracker m_appenderTracker;

    public PaxLoggingConfigurator( AppenderTracker appenderTracker )
    {
        m_appenderTracker = appenderTracker;
    }

    Appender parseAppender( Properties props, String appenderName )
    {
        if (appenderName.startsWith( OSGI_APPENDER_PREFIX )) {
            appenderName = appenderName.substring(
OSGI_APPENDER_PREFIX.length() );
            PaxAppender appender =
m_appenderTracker.getAppender( appenderName );
            return new AppenderBridgeImpl( appender );
        }
        else
        {
            return super.parseAppender( props, appenderName );
        }
    }
}


The super class is PropertyConfigurator, which is this:

public class PropertyConfigurator
    implements Configurator
{

    public PropertyConfigurator()
    {
    }

    public static void configure( String filename )
    {
        // dummy, ignore
    }

    public static void configure( URL url )
    {
        // dummy, ignore
    }

    public static void configure( Properties properties )
    {
        // dummy, ignore
    }

    public static void configureAndWatch( String filename )
    {
        // dummy, ignore
    }

    public static void configureAndWatch( String filename, long
timeout )
    {
        // dummy, ignore
    }
}



There is no parseAppender method, so obviously this won't compile.

Now, the bundle works, so what strange magic are you using to pull this
off?


Thanks!
=David.Leangen




_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general