I am working in an application consisting of 3 to 4 spring configuration file. Each file has many bean definitions.
I am using JBoss to deploy the application. But if there occurs some problem in the bean instantion from the spring configuration file, my application is not getting deployed.
Is there any way by which we can test configuration file which consist spring bean definitions, so that I can confidently deploy in JBoss?
SCJP,SCWCD, Into ATG now!
Joined: Aug 31, 2006
A unit test that loads the ApplicationContext ought to do it. While you are at it you could attempt to pull each Bean and make sure you get them and they are of the correct type.
Joined: Jun 16, 2011
I agree with Tim that a unit test should load it. But that being said, it won't test everything because unit test will detect problems involving the beans that you try to load in your test . The best way i found to test the configuration is using JUnit with an open-source project called Beanoh and it's in github it was extremely easy to use
and this basically will go through all the beans defined in a bootstrap spring context (by default it looks for com.somepackage.SomeTest-BeanohContext.xml ) and one by one it attempts to load them which will throw an exception if spring cannot load the beans correctly .... Beanoh also has another test for @component annotated classes and detecting duplicate bean ids ... really helpful