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

Marcel Offermans commented on ACE-401:
--------------------------------------

The configurator has a built-in mechanism that allows it to substitute 
parameters. They use a syntax like: ${parametername} and it seems the parser 
that handles this syntax gets confused by the "}" characters (in the substVars 
method). At the moment I don't see a way to somehow "escape" these characters 
to indicate you want to have them literally added to the configuration file, so 
I don't see an easy workaround for now.

We should add a test case for this though, and come up with a solution.
                
> ACE configurator throws exception when consuming logging property file
> ----------------------------------------------------------------------
>
>                 Key: ACE-401
>                 URL: https://issues.apache.org/jira/browse/ACE-401
>             Project: ACE
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Wilfried Sibla
>
> Exception in thread "Apache ACE Configurator" 
> java.lang.IllegalArgumentException: stop delimiter with no start delimiter: 
> %d{ISO8601} | %-5.5p | %C | %X{bundle.name} | %m%n
>       at 
> org.apache.ace.configurator.Configurator.substVars(Configurator.java:369)
>       at 
> org.apache.ace.configurator.Configurator.substVars(Configurator.java:307)
>       at 
> org.apache.ace.configurator.Configurator.processConfigFile(Configurator.java:201)
>       at 
> org.apache.ace.configurator.Configurator.doConfigs(Configurator.java:151)
>       at org.apache.ace.configurator.Configurator.run(Configurator.java:121)
>       at java.lang.Thread.run(Thread.java:722)
> This line from the cfg file causes the exception:
> log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} | %-5.5p | %C | 
> %X{bundle.name} | %m%n

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to