Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 357583
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T12:13:09+00:00 2026-05-12T12:13:09+00:00

Dependency injection is a useful technique but what approach is recommended when faced with

  • 0

Dependency injection is a useful technique but what approach is recommended when faced with runtime dependencies?

e.g. Say you want to glue an event to an event processor depending on the type of the event and the user who initiated the request.

public interface Event {}

public interface EventProcessor {
    public void handleEvent(Event e);
}

class EventProcessorFactory {
    private final User u;
    private final Event e;

    public EventProcessorFactory(User u, Event e) {
        this.u = u;
        this.e = e;
    }

    public EventProcessor get() {
        EventProcessor ep;
        if(e instanceof LocalEvent) {
            ep = new LocalEventProcessor();
        }
        else if(e instanceof RemoteTriggeredEvent && u instanceof AdminUser) { 
            //has static dependencies
            ep = new RemoteEventProcessor(u);
        }
        else {
            ep = new DefaultEventProcessor();
        }
    }
}

Now the complexity is encapsulated in the factory, but how else could I achieve the same result, without too much boilerplate code?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T12:13:09+00:00Added an answer on May 12, 2026 at 12:13 pm

    You could use something like

    public interface EventProcessor {
        public boolean supports(Event event, User user);
        public void handleEvent(Event event);
    }
    
    class EventProcessorFactory {
        public void setEventProcessors(List<EventProcessor> processors) {
            this.processors = processors;
        }
        public EventProcessor get(Event event, User user) {
            for (EventProcessor processor : processors) {
                if (processor.supports(event, user)
                    return processor;
            }
        }
    }
    
    class LocalEventProcessor implements EventProcessor {
       public boolean supports(Event event, User user) {
            return (event instanceof LocalEvent);
       }
       // etc
    }
    
    class RemoteEventProcessor implements EventProcessor {
        public boolean supports(Event event, User user) {
            return (event instanceof RemoteTriggeredEvent) &&
                   (user instanceof AdminUser);
        }
        // etc
    }
    

    If your processors have some sort of natural ordering, you can implement Comparable to ensure they are tested in the correct order, otherwise you’ll can rely on them being injected into the factory in the required order, thus making it configurable.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a question regarding dependency injection. say i want to create a class
I want to use dependency injection (Unity) and at the moment I'm thinking about
When using IoC for dependency injection the most recommended use is constructor injection (as
Which Dependency Injection frameworks are compatible (and tested) against the Mono 2.4.2.3 runtime (
Dependency injection seems to be a good thing. In general, should dependencies be injected
Which C#/.NET Dependency Injection frameworks are worth looking into? And what can you say
Do we achieve Dependency Inversion Principle using Dependency Injection technique? Am I correct?
I am a big fan of Dependency Injection and the Play Framework, but am
I understand dependency injection, but have not had that ah moment, where it clicks
Interface Builder can be used for basic dependency injection in a Cocoa app, but

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.