Re: Custom appender : PluginElement

2014-09-06 Thread lb
I did a test but if the @PluginElement does not match @Plugin it fails with: 2014-09-06 14:22:26,335 ERROR BinaryVanillaChronicle contains an invalid element or attribute chronicleConfig 2014-09-06 14:22:26,341 ERROR TextVanillaChronicle contains an invalid element or attribute chronicleConfig

Re: Custom appender : PluginElement

2014-09-06 Thread Matt Sicker
Alright. That would mean you need to use @PluginAliases if you want to support other element names besides the plugin name. The JMS Appender is actually using that right now in the master branch. On 6 September 2014 07:26, lb lburgazz...@gmail.com wrote: I did a test but if the @PluginElement

Re: Custom appender : PluginElement

2014-08-31 Thread lb
I think you should explicit state that every @PluginElement should be a Plugin then it is clear. As consequence, there is a little problem as you can't have two nested elements with the same name, i.e. AppenderA Configuration /Configuration /AppenderA AppenderB Configuration

Re: Custom appender : PluginElement

2014-08-31 Thread Matt Sicker
I think you can use different values for @PluginElement than you do for @Plugin which helps in the XML/JSON format. I'd have to look into this more. On 31 August 2014 10:23, lb lburgazz...@gmail.com wrote: I think you should explicit state that every @PluginElement should be a Plugin then it

Re: Custom appender : PluginElement

2014-08-30 Thread lb
Yes that was the problem, I forgot to mark it as plugin. Now it works, thank you On Friday, August 29, 2014, Matt Sicker boa...@gmail.com wrote: Is VanillaLogAppenderConfig also marked as a @Plugin and everything? On 28 August 2014 05:13, lb lburgazz...@gmail.com javascript:; wrote: I'm

Re: Custom appender : PluginElement

2014-08-29 Thread Matt Sicker
Is VanillaLogAppenderConfig also marked as a @Plugin and everything? On 28 August 2014 05:13, lb lburgazz...@gmail.com wrote: I'm writing a custom appender and I have a problem setting up PluginElement: The xml definition is the following one: BinaryVanillaChronicle

Re: Custom appender : PluginElement

2014-08-29 Thread Remko Popma
It could be a problem with log4j2 not loading your custom plugin correctly. It looks like you are building with maven. Does the jar file generated by your build contain a META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat file? If it doesn't you could try specifying the

Custom appender : PluginElement

2014-08-28 Thread lb
I'm writing a custom appender and I have a problem setting up PluginElement: The xml definition is the following one: BinaryVanillaChronicle name=CONF-BINARY-VANILLA-CHRONICLE path${sys:java.io.tmpdir}/chronology-log4j2/conf-binary-vanilla-chronicle/path formatMessagefalse/formatMessage