Hi Remko,
I've found out that class
org.apache.logging.log4j.core.config.plugins.ResolverUtil is using
org.osgi.framework.wiring.BundleWiring class, and, as I know
org.osgi.framework.wiring package is available only in osgi.core jar version
4.3.0 or higher. I can use only osgi.core verison 4.2.0
I see... Did you try pre-building the binary file with plugin descriptors using
the PluginManager main method?
It may be possible (but a bit of a hack) to use async loggers without
reflection. It involves compiling your own version of the
com.lmax.disruptor.util.Util class where you replace the implementation of the
#getUnsafe() method with a simple call to sun.misc.Unsafe.getUnsafe().
Obviously this is
Are the test programs identical? I
Yes identical excepting for log4j versions and the required totally different
way of configuring.
MDC
Not coded this yet, wanting to in one version or the other. So no code to post
since I haven't gotten to MDC vs NDC (??) yet. Just making sure going to
Sorry,
Do you mean binary file of my custom appender?
-Original Message-
From: Remko Popma [mailto:rem...@yahoo.com]
Sent: Tuesday, July 30, 2013 2:09 PM
To: Log4J-Users List
Subject: Re: Are the custom appenders only like plugins?
I see... Did you try pre-building the binary file with
No. See http://logging.apache.org/log4j/2.x/manual/plugins.html and then the
section on plugin pre-loading.
Ralph
On Jul 30, 2013, at 7:56 AM, Aliaksandr Belavusau wrote:
Sorry,
Do you mean binary file of my custom appender?
-Original Message-
From: Remko Popma
Sorry for being unclear. I#x27;ve explained it better in this Jira comment:
https://issues.apache.org/jira/browse/LOG4J2-232?focusedCommentId=13648502page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13648502
