By design, programmatic refreshing of an ApplicationContext is not explicitly supported by the Spring TestContext Framework. Furthermore, it is not intended that a test method refresh a context. Thus I would recommend that you reassess your need for a refresh and consider alternatives like placing test methods that require a different set of active profiles … Read more
Option 1 (should be preferred as it’s the best practice): Refactor your config files under WEB-INF and move the common parts (that you want to access also from integration tests) to src/main/resources/. Then write test specific configuration files in src/test/resources/ (if you only need to import several different config files from src/main to assemble your … Read more
Previous comments are ok, but I usually prefer: @Autowired private ApplicationContext applicationContext;
To expand on the @PostConstruct suggestion in other answers, this really is the best solution, in my opinion. It keeps your code decoupled from the Spring API (@PostConstruct is in javax.*) It explicitly annotates your init method as something that needs to be called to initialize the bean You don’t need to remember to add … Read more
Create in onCreate() an instance of getApplicationContext() (mContext) then call MyApp.getContext() from everywhere in your app and you will get your application context statically. public class MyApp extends Application { private static Context mContext; public static Context getContext() { return mContext; } @Override public void onCreate() { super.onCreate(); mContext = getApplicationContext(); } } Remember to … Read more
Thanks, but that was not the solution. I found it out why it wasn’t working for me. Since I’d done a declaration: ApplicationContext context = new ClassPathXmlApplicationContext(“beans.xml”); I thought I would refer to root directory of the project when beans.xml file was there. Then I put the configuration file to src/main/resources and changed initialization to: … Read more
Spring has some standard events which you can handle. To do that, you must create and register a bean that implements the ApplicationListener interface, something like this: package test.pack.age; import org.springframework.context.ApplicationContext; import org.springframework.context.ApplicationEvent; import org.springframework.context.ApplicationListener; import org.springframework.context.event.ContextRefreshedEvent; public class ApplicationListenerBean implements ApplicationListener { @Override public void onApplicationEvent(ApplicationEvent event) { if (event instanceof ContextRefreshedEvent) { ApplicationContext … Read more
If the object that needs access to the container is a bean in the container, just implement the BeanFactoryAware or ApplicationContextAware interfaces. If an object outside the container needs access to the container, I’ve used a standard GoF singleton pattern for the spring container. That way, you only have one singleton in your application, the … Read more
The spring docs are great on this: 3.8.1. BeanFactory or ApplicationContext?. They have a table with a comparison, I’ll post a snippet: Bean Factory Bean instantiation/wiring Application Context Bean instantiation/wiring Automatic BeanPostProcessor registration Automatic BeanFactoryPostProcessor registration Convenient MessageSource access (for i18n) ApplicationEvent publication So if you need any of the points presented on the Application … Read more
I’m sure you’ve moved on by now, but I thought I’d answer anyway. Some of these answers give workarounds. What actually must happen is that you clean and re-publish your project to “activate” the new URI. This is done by right-clicking your server (in the Servers view) and choosing Clean. Then you start (or restart … Read more