[
https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068599#comment-14068599
]
Remko Popma commented on LOG4J2-728:
------------------------------------
Isn't that essentially creating our own file system abstraction? I'd like to
keep it as light-weight as possible.
An alternative that I can see is to create a subclass of
{{XmlConfigurationFactory}}, and override the {{protected ConfigurationSource
getInputFromUri(URI configLocation)}} method. In the Android-specific
implementation you would use Android-specific APIs to load the log4j2.xml file
from the specified configLocation.
You can tell log4j to use your custom configuration factory by setting system
property {{log4j.configurationFactory}} or by
calling the static method
{{ConfigurationFactory.setConfigurationFactory(ConfigurationFactory)}} (before
creating any Logger instances).
> Look for log4j2.xml in assets folder (or the application data) in an Android
> APK.
> ---------------------------------------------------------------------------------
>
> Key: LOG4J2-728
> URL: https://issues.apache.org/jira/browse/LOG4J2-728
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-rc2
> Environment: Android
> Reporter: Nelson MELINA
> Labels: android
>
> To add files in an Android apk, you need to put them in an assets folder and
> then they are in an "assets" folder in the APK.
> Log4j 2 needs to find it there when it exists (not the case now).
> Also would it be possible to load the xml configuration file from the
> application data (
> https://developer.android.com/guide/topics/data/data-storage.html ) ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
