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 798141
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T22:55:23+00:00 2026-05-14T22:55:23+00:00

I am dynamically creating classes which contain spring beans, however the beans are not

  • 0

I am dynamically creating classes which contain spring beans, however the beans are not getting instantiated or initialised, leaving them as null.

How do I make sure that a dynamically created class creates all of its spring beans properly?

This is how I am dynamically creating the class:

Class ctransform;
try {
    ctransform = Class.forName(strClassName);
    Method handleRequestMethod = findHandleRequestMethod(ctransform);
    if (handleRequestMethod != null) {
        return (Message<?>) handleRequestMethod.invoke(ctransform.newInstance(), message);
            }
    }

This leaves all spring bean objects within ctransform (of type strClassName) as null.

  • 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-14T22:55:24+00:00Added an answer on May 14, 2026 at 10:55 pm

    Whenever you instantiate classes, they are not spring-managed. Spring has to instantiate classes so that it can inject their dependencies. This with the exception of the case when you use @Configurable and <context:load-time-weaver/>, but this is more of a hack and I’d suggest against it.

    Instead:

    • make the bean of scope prototype
    • obtain the ApplicationContext (in a web-app this is done via WebApplicationContextUtils.getRequiredWebApplicationContext(servletContext))
    • if the classes are not registered (and I assume they are not), try casting to StaticApplicationContext (I’m not sure this will work), and call registerPrototype(..) to register your classes in the context. If this doesn’t work, use GenericContext and its registerBeanDefinition(..)
    • get all the instances that match your type, using appContext.getBeansOfType(yourclass); or if you just registered it and know its name – use just appContext.getBean(name)
    • decide which one is applicable. Usually you will have only one entry in the Map, so use it.

    But I would generally avoid reflection on spring beans – there should be another way to achieve the goal.


    Update: I just thought of an easier solution, that will work if you don’t need to register the beans – i.e. that your dynamically generated classes won’t be injected in any other dynamically generated class:

    // using WebApplicationContextUtils, for example
    ApplicationContext appContext = getApplicationContext(); 
    Object dynamicBeanInstance = createDyamicBeanInstance(); // your method here
    appContext.getAutowireCapableBeanFactory().autowireBean(dynamicBeanInsatnce);
    

    And you will have your dependencies set, without having your new class registered as a bean.

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

Sidebar

Ask A Question

Stats

  • Questions 434k
  • Answers 434k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer This is just a string like any other string. Once… May 15, 2026 at 3:10 pm
  • Editorial Team
    Editorial Team added an answer It's simple to do in XSLT. Add this to the… May 15, 2026 at 3:10 pm
  • Editorial Team
    Editorial Team added an answer The only way to do this that I've figured out… May 15, 2026 at 3:10 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.