DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • 5 Layers of Prompt Injection Defense You Can Wire Into Any Node.js App
  • Preventing Prompt Injection by Design: A Structural Approach in Java
  • Algorithmic Circuit Breakers: Engineering Hard Stop Safety Into Autonomous Agent Workflows
  • Why Every Defense Against Prompt Injection Gets Broken — And What to Build Instead

Trending

  • LLM Agents and Getting Started with Them
  • The Hidden Cost of Overprivileged Tokens: Designing Messaging Platforms That Assume Compromise
  • Designing API-First EMR Architectures in .NET: Enabling Modular Growth in Compliance-Driven Systems
  • S3 Vectors: How to Build a RAG Without a Vector Database
  1. DZone
  2. Coding
  3. Frameworks
  4. Logger Injection With Spring’s InjectionPoint

Logger Injection With Spring’s InjectionPoint

If you have a tendency to use Logger instances, see how you can set up a way to inject them into your features at runtime.

By 
Fatih Dirlikli user avatar
Fatih Dirlikli
·
Nov. 27, 16 · Tutorial
Likes (8)
Comment
Save
Tweet
Share
28.3K Views

Join the DZone community and get the full member experience.

Join For Free

You should all be familiar with the boiler plate code you include on top of your classes to get a Logger instance for use in your classes at runtime.

Logger logger = LoggerFactory.getLogger(WorkOrderController.class);

This is the classic way of obtaining a logger instance at runtime with the classname that you want to be displayed in your log messages like below.

2016-11-22 14:48:37.025 ERROR --- org.orwashere.WorkOrderController : My Service got the request!!

The fully qualified class name org.orwashere.WorkOrderController is retrieved and logged from the class parameter you pass to LoggerFactories getLogger class.

With Spring Framework’s new InjectionPoint feature you can get rid of these boiler plate code in your classes. All you need to do is declaring a prototype scoped Logger bean in one of your configuration classes like below. And from that point, you have access to the class’s properties that the Logger bean is being injected to. As we should be creating a new Logger instance for each Spring Bean that we want to enable logging, it is important to define the Logger bean as prototype scoped.

@Bean
@Scope("prototype")
Logger logger(InjectionPoint injectionPoint){
    return LoggerFactory.getLogger(injectionPoint.getMethodParameter().getContainingClass());
}

In your class target bean in which the logger will actually be used all you need to do is injecting the Logger bean as a classic Spring Bean and voila your logger is configured and ready to be used in your class like below.

@RepositoryRestController
public class WorkOrderController {

    private static Logger logger;

    public WorkOrderController(Logger logger) {
        this.logger = logger;
    }

    public void myControllerMethod() {
        logger.error("My service got the request!");
    }   
}

Even though we are talking about Logger injection in this post, with InjectionPoint support many other opportunities arise before injecting any bean into your class. Basically you can make any kind of configuration on your injected bean depending on the target bean.

Hope it helps you in your future development!

Happy coding!

Spring Framework Injection

Published at DZone with permission of Fatih Dirlikli. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • 5 Layers of Prompt Injection Defense You Can Wire Into Any Node.js App
  • Preventing Prompt Injection by Design: A Structural Approach in Java
  • Algorithmic Circuit Breakers: Engineering Hard Stop Safety Into Autonomous Agent Workflows
  • Why Every Defense Against Prompt Injection Gets Broken — And What to Build Instead

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook