[
https://issues.apache.org/jira/browse/LOG4J2-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897475#comment-16897475
]
Ralph Goers edited comment on LOG4J2-2649 at 7/31/19 7:42 PM:
--------------------------------------------------------------
Take a look at PropertiesUtil and ProviderUtil. You will find that they both
use ServiceLoader. What you probably don't like is that ServiceLoader isn't
being used to load the LoggerContextFactory. That is because Log4j wants to
make sure the implementation it found matches the API version being asked for.
ServiceLoader can't do that by itself so the service being loaded has that
information along with the LoggerFactory class to be used.
was (Author: [email protected]):
Take a look at PropertiesUtil and ProviderUtil. You will find that they both
use ServiceLoader.
> Is Log4j2 considered to support successful static compilation under GraalVM?
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-2649
> URL: https://issues.apache.org/jira/browse/LOG4J2-2649
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: YangGuanchao
> Priority: Blocker
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Oracle released GraalVM [https://github.com/oracle/graal] to support the
> static compilation of Java applications to Native Image, which can increase
> the startup speed of Java by at least 10 times. In the cloud native field,
> this basic technology is believed to be in the near future. Will be supported
> by more and more vendors, such as the Spring/Spring Boot community has
> supported or plans to support the feature of GraalVM, see this issue:
> [https://github.com/spring-projects/spring-framework/search?q=Graalvm&type=Issues]
> can support static compilation, so it is recommended that Log4j2 also need
> to support static compilation as soon as possible, and can be compiled
> correctly under GraalVM.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
