Anyway, even without the stack trace, we can assume that your custom appender will be instantiated by calling the instantiateByClassName(String, Class, Context) method in OptionHelper (line 36). This method assumes that you want to use the class loader which loaded the current logback context to be used. (This is usually the same class loader that loaded all other logback classes as well.) Thus, you have to make sure that the said class loader can load foo.RCPAppender. Can you do that? -- Ceki http://twitter.com/#!/ceki On 24.05.2012 14:20, David Virdefors wrote:
Hi,
It seems like there is no built in support for logging from within an Eclipse RCP plug-in. So I wrote my own appender and pointed to it from my logback.xml
14:14:04,992 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not create an Appender of type [foo.RCPAppender]. ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type se.ericsson.baseband.logging.RCPAppender
at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type foo.RCPAppender
I’ve seen other people who have trouble with this when using ecilpse plug-ins and bundles due to different class loaders. I have however not found any proper solution to this.
How would I make logback find my appender?
BR David
*From:*logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] *On Behalf Of *David Virdefors *Sent:* den 24 maj 2012 11:41 *To:* logback-user@qos.ch *Subject:* [logback-user] RCP
Hi,
I’m developing Eclipse RCP plug-ins. Is it possible to make logback log to the existnig workspace log, so that the logs show up in the ”Error Log” view in the GUI?
BR David