Hi,
I can't seem to get the DefaultRolloverStrategy to work with the following
configuration. Is there anything I am doing wrong?
Thanks,
Arkin
On Mon, Oct 14, 2013 at 11:10 AM, Ralph Goers
wrote:
>
> On Oct 14, 2013, at 7:31 AM, Gary Gregory wrote:
>
>> The current idea I have is that the XML Schema would reflect exactly
>> the code that is running. We should start with that. AFAIK, the
>> current code we have does not allow open-ended
On Oct 14, 2013, at 7:31 AM, Gary Gregory wrote:
> The current idea I have is that the XML Schema would reflect exactly
> the code that is running. We should start with that. AFAIK, the
> current code we have does not allow open-ended XML fragments, but I
> could be wrong...
>
> Gary
Of course
The current idea I have is that the XML Schema would reflect exactly
the code that is running. We should start with that. AFAIK, the
current code we have does not allow open-ended XML fragments, but I
could be wrong...
Gary
On Mon, Oct 14, 2013 at 10:25 AM, wrote:
> So basically when you want s
So basically when you want strict validation you want it really strict, i.e.
not only for the base types like appenders, filters but also their attributes?
As far as I understand that would result in a bigger schema where each type is
defined in the schema and the config looks more like the non-s
Alexander ,
XML validation against the XML Schema is not fully baked because the
Log4j 2 XML Schema is incomplete. Due to the current dynamic nature of
the configuration file (it's schema is tied to the Java code and the
annotations used), we need to generate the XML Schema based on these
annotati
Hi,
I'm using log4j2-beta9 and want to configure it using a log4j2.xml in strict
mode. My issue is: how do I specify attributes that are not in the shipped
schema file? An Example:
http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="Log4j-config.xsd">
