Why use Spring ApplicationContext hierarchies?

I am trying to understand ApplicationContext hierarchies in spring.

I learned the following

1. An ApplicationContext cannot have more than 1 parent ApplicationContext.
2. When a given ApplicationContext cannot resolve a bean, it will pass on the resolution request to its parent.
3. The parent of an ApplicationContext is specified in its constructor.

I would like to unde开发者_如何转开发rstand when to use ApplicationContext hierarchies (instead of a single ApplicationContext).

The best I could get from google was this. And what I understand is that if an application has a large number of beans defined at the various layers then each layer having its own ApplicationContext would be a benefit. What is not understood is what is the benefit of doing so and how is the benefit achieved?

The classic use-case for this is when you have multiple Spring DispatcherServlet within a single webapp, with each of these servlets having their own app context, but which need to share beans between them. In this case, you add a 3rd context at the level of the webapp, which is the parent of each of the servlet appcontexts.

You can take this pattern further, for example if you have multiple webapps bundled into a single JavaEE EAR. Here, the EAR can have its own context, which is the parent of the individual webapp contexts, which is the parent of the servlet contexts, and so on. You have this hierarchy of responsibility.

In other situations, the context structure is dictated by some other factor. For example, Spring Security is independent of Spring MVC, and requires its configuration beans to go in the webapp context. If you want to use Spring MVC with it, then the config for that has to go into the servlet context, which has the root webapp context as its parent.