[
https://issues.apache.org/jira/browse/LOG4J2-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342914#comment-14342914
]
Johannes Siebel edited comment on LOG4J2-962 at 3/2/15 8:38 AM:
----------------------------------------------------------------
Yes. I've added that information to the ticket. I'm also using Weld SE in the
same application and I'm not sure if there's some possibility that these
components' interfere with each others functionality.
was (Author: [email protected]):
Yes, I've added that information to the ticket.
> Main Arguments Lookup not working
> ---------------------------------
>
> Key: LOG4J2-962
> URL: https://issues.apache.org/jira/browse/LOG4J2-962
> Project: Log4j 2
> Issue Type: Bug
> Components: Lookups
> Affects Versions: 2.1
> Environment: Windows 7 x64, Java Batch Application
> Reporter: Johannes Siebel
>
> It is not possible to use the Main Arguments Lookup in the current version.
> The "main" prefix is not present in the corresponding Interpolator object and
> thus the resolution of the variable is not working as advertised in the
> documentation, e.g. using in the log4j2.xml:
> {code}${main:0}{code}
> As far as I can tell, the problem seems to stem from the
> PluginManger.collectPlugins-Method that does not acknowledge the existence of
> the Main Arguments Lookup.
> I'm following the documentation on the website with the following sample
> log4j2.xml:
> {code:xml}
> <File name="GLOBAL" fileName="${env:DATA_DIR}/log/${env:APP_NAME}.log" >
> <PatternLayout pattern="%m%n" header="File: ${main:0}" />
> ...
> {code}
> And following code in my Main Application:
> {code}
> MapLookup.setMainArguments(args);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
