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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T06:01:35+00:00 2026-05-28T06:01:35+00:00

Typically there is one ApplicationContext (parent) and 0..n DispatcherServlets (children). Is it also possible

  • 0

Typically there is one ApplicationContext (parent) and 0..n DispatcherServlets (children). Is it also possible to have aDispatcherServlet that has another DispatcherServlet as parent context which has the ApplicationContext as parent? As I understood, beans can be resolved transitively so it should be possible to access the application context.

I don’t want to put the shared beans into the ApplicationContext because they must not be exposed to other DispatcherServlet – with one exception.

  • 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-28T06:01:35+00:00Added an answer on May 28, 2026 at 6:01 am

    I extended the DispatcherServlet. Now it works perfectly!

    public class ConfigurableDispatcherServlet extends DispatcherServlet {
    
        private String contextParent;
    
        /**
         * Initialize and publish the WebApplicationContext for this servlet.
         * <p>
         * Delegates to {@link #createWebApplicationContext} for actual creation of
         * the context. Can be overridden in subclasses.
         * 
         * @return the WebApplicationContext instance
         * @see #setContextClass
         * @see #setContextConfigLocation
         */
        protected WebApplicationContext initWebApplicationContext() {
            // No fixed context defined for this servlet - create a local one.
            WebApplicationContext parent = WebApplicationContextUtils.getWebApplicationContext(getServletContext(),
                    "org.springframework.web.servlet.FrameworkServlet.CONTEXT." + getContextParent());
            WebApplicationContext wac = createWebApplicationContext(parent);
    
            // Publish the context as a servlet context attribute.
            String attrName = getServletContextAttributeName();
            getServletContext().setAttribute(attrName, wac);
            if (this.logger.isDebugEnabled()) {
                this.logger.debug("Published WebApplicationContext of servlet '" + getServletName() +
                            "' as ServletContext attribute with name [" + attrName + "]");
            }
            if(this.logger.isInfoEnabled()) {
                this.logger.info(getServletName() + " is a child of " + parent.getDisplayName());
            }
    
            return wac;
        }
    
        public String getContextParent() {
            return contextParent;
        }
    
        public void setContextParent(String contextParent) {
            this.contextParent = contextParent;
        }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Typically I create a plugin when I have a module that I know I'm
I have an ASP.NET MVC application that has a jQuery Treeview and a jQuery
I have a List object being accessed by multiple threads. There is mostly one
I know there are posts that ask how one stores third-party libraries into source
I have read a lot about preventing race conditions, but typically with one record
Disk benchmarks typically have a chart that shows the I/O throughput increasing as the
In my python script i am parsing a user created file and typically there
I am working with your typical three layered application that has a presentation layer,
Typically when writing new code you discover that you are missing a #include because
Typically I use E_ALL to see anything that PHP might say about my code

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.