In certain J2EE environments with the collocation of multiple enterprise projects, it is possible for log4j API to be visible in the CLASSPATH of component A while the library is actually from component B. In such cases, DN in component A defaults to log4j API per rules described @ http://www.datanucleus.org/products/accessplatform_1_1/logging.html
and if component A is designed to use a different logging API such as JDK14, there seems to be no way to configure DN to use the desired logging API.
Is it possible to create an optional property such as
so that an override of CLASSPATH-driven behavior can be made?