Thanks for the reply, 

It turns out the problem was I wasn't including the

log4j.categoryFactory=com.foo.MyCategoryFactory

property in my setup even.

 

-----Original Message-----
From: Kitching Simon [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 12:13 PM
To: 'LOG4J Users Mailing List'
Subject: RE: Configuration question.


Hi Jeff,

By default, the configurator will create
Category objects of the default type.

Have you told the configurator to create instances of 
your custom Category? If not, and you are (elsewhere) 
trying to cast this Category object to your custom class
then it will generate a ClassCastException.

I forget how you override the created Category type,
but it's in the docs for whatever configurator type you're using.

Hope this helps...

Simon

> -----Original Message-----
> From: Jeff Wrana [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, February 27, 2001 9:12 PM
> To:   '[EMAIL PROTECTED]'
> Subject:      Configuration question.
> 
> I am encountering problems where configuration properties aren't
> recognized
> when setting priority to specific category. I have overridden the Category
> class with my own MyCategory (as well as the factories and parsers) 
> 
> the usual convention for specifying a priority for Category is 
> 
> log4j.category.com.java.whatever=FATAL
> 
> I have tried this but get a runtime ExceptionInInitializer exception. Is
> this the correct way but I am forgetting to code something in my
> MyCategory
> class? or is there a another correct way to set the property when using
> subclasses of Category? 
> 
> thank
> Jeff
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to