[ 
https://issues.apache.org/jira/browse/LOG4J2-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708486#comment-14708486
 ] 

Charles Leclerc commented on LOG4J2-1100:
-----------------------------------------

There is no schma language for YAML. Even if there were you would hit the same 
problems as strict/non-strict XML file.

JSON and YAML make a difference between maps and sequence; XML doesn't. This 
caused the error and could have occured exactly the same way with JSON.

Given the structure of the configuration system, it won't be easy to have a 
more precise error message. Perhaps it would be simpler to just put a little 
bit more details in it (what's excpected in the Policies element and what has 
been found).

> Unable to configure Multiple triggering policies on rolling file appender 
> using yaml configuration file
> -------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1100
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1100
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.3
>            Reporter: Charles Leclerc
>            Priority: Minor
>         Attachments: log4j2.json, log4j2.xml, log4j2.yaml
>
>
> I wanted to use yaml instead of XML for better lisibility of the 
> configuration. I tried the attached log4j2.yaml configuration file and when 
> running the application I have the following error in the console :
> {noformat}
> 2015-08-21 11:25:26,052 ERROR appender RollingFile has no parameter that 
> matches element Policies
> {noformat}
> I tried different changes but had no success. From what I understand the 
> configuration below seems to be correct, but I may be wrong. The XML and JSON 
> version of my configuration (also attached to this issue) work fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to