ppkarwasz commented on issue #3770:
URL: 
https://github.com/apache/logging-log4j2/issues/3770#issuecomment-2995877087

   Hi @wilkinsona,
   
   Thanks — I’ve added some suggestions to the discussion in 
spring-projects/spring-boot#46035.
   
   Spring Boot is one of the projects that makes the most extensive use of the 
API surface exposed by Log4j Core, and we’re very mindful of which methods are 
being used. We try to document these methods, so we can avoid surprises like 
the removal of `ConfigurationFactory.getConfiguration(ConfigurationSource)` in 
2.7 — an experience we definitely don't want to repeat with Log4j Core 3. 
Apparently we missed one method :wink:
   
   That said, there are still some areas we’d like to revisit or better 
abstract. One example is Spring Boot’s current reliance on relatively internal 
classes like `AuthorizationProvider` and `SslConfiguration`. Ideally, these 
could be abstracted in a way that allows tighter integration with Spring Boot’s 
own mechanisms for managing secrets and credentials.
   
   Our `ShutdownCallbackRegistry` could also benefit from tighter integration 
with Spring Boot, to ensure that the logging system is shut down **last**, 
after all other components have completed their cleanup. The current 
`DefaultShutdownCallbackRegistry` relies on JVM shutdown hooks, which do not 
guarantee any specific execution order. If I recall correctly, Spring Boot 
currently disables the default shutdown hook entirely — which makes sense, but 
also highlights the need for a more coordinated and flexible shutdown mechanism.
   
   If you have time and are open to a deeper discussion, feel free to reach out 
via the email listed on [my GitHub profile](https://github.com/ppkarwasz), or 
schedule a quick chat using my [zeeg.me link](https://zeeg.me/).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to