Comments on: Spring application context loading tricks

By: Ben

Ben — Wed, 26 May 2010 13:36:55 +0000

Manish,

In my experience the JVM doesn’t lie to you when reporting errors. If it’s throwing a FileNotFoundException, the file simply isn’t being found.

I’d start by checking out options to print the classpath on server and application start (there’s sure to be a diagnostic option for this), then take a good look at your package. From your description I’m willing to bet your second project package isn’t on the classpath of the first.

By: Manish

Manish — Tue, 25 May 2010 09:21:01 +0000

related to SOM’s Question, I am trying to use 2 XML files in application context – one is in the same project and 2nd in another project. This 2nd project has been added to my current project and the context in web.xml is

contextConfigLocation

/WEB-INF/eu24ui-servlet.xml
classpath:spring-ds.xml
classpath:spring-hibernate-iocm.xml

But when I try to start the jboss server.. it throws fileNotFoundException.
Need help.

By: Denis

Denis — Thu, 13 Aug 2009 09:12:07 +0000

Hi Ben,

Very nice article. I was looking for the answer described in “Do not ever do this” where I have multiple modules with same application context name. I will use module specific names.

By: Ben

Ben — Wed, 31 Dec 2008 13:32:59 +0000

Som,

If you want to load files from two different locations using wildcards, the classpath*:-notation is the way to go.

As for your cross-contextfile dependencies, those will always work; that’s a function of the Spring container. The thing to understand is that you do not get a context PER FILE — no matter how many context FILES you have, the Spring container always loads them all together and makes one single CONTEXT out of them before initializing your beans. The only way to have multiple contexts in a program is to have the program start two separate instances of the Spring container.

By: Som

Som — Wed, 31 Dec 2008 05:57:24 +0000

What if I want to load two application context files with dependencies like applicationContextTwo uses beans in applicationContextOne and both are in different classpaths.

By: Goran

Goran — Mon, 26 May 2008 14:49:34 +0000

Hehe Ben like always a great read Thanks!

By: Ben

Ben — Sun, 18 May 2008 02:59:39 +0000

I agree with Uri. Note that my post was intended as an overview and not so much as a recommendation.

By: Uri

Uri — Wed, 14 May 2008 07:04:55 +0000

An advantage of explicitly defining the actual application context names (without wildcards) is that it provides you with yet another view of your layered architecture. I personally like to have an application context per layer (e.g. service-layer.xml, data-access-layer.xml, etc…) and each one of these application context is composed out of more functional ones. so all thing related to messaging I would put in messaging.xml and import it in the service-layer.xml context.

cheers,
Uri