The configuration factory is responsible for parsing a config file and creating
a Configuration object. As such, it must exist _before_ the configuration file
is processed.
Log4j plugins are only created during processing of the config file. So a
configuration factory cannot be a plugin.
Best regards,
Remko
Sent from my iPhone
> On 2014/08/01, at 10:18, Clément Guillaume <cguilla...@hotpads.com> wrote:
>
> Hi,
>
> I'm trying to use a custom ConfigurationFactory. I created and annotated it
> with a @Plugin and an @Order like this:
>
> @Plugin(category = "ConfigurationFactory", name =
> "StartupConfigurationFactory")
> @Order(10)
> public class StartupConfigurationFactory extends ConfigurationFactory{
> ...
> }
>
> But it is never loaded (none of the 2 methods are called).
>
> If I specify the system property "log4j.configurationFactory" with the name
> of my class before creating a logger, my factory is successfully loaded.
>
> Did I made a mistake declaring my ConfigurationFactory ?
>
> Clément
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
