I have the same issue, and tried a 'workaround':
Make your controller implement ApplicationContextAware. This causes the method:
public void setApplicationContext(ApplicationContext applicationContext)
to be called with the ApplicationContext object.
You can then use this to access the bean defined in applicationcontext.xml:
Example (method in controller):
public void setApplicationContext(ApplicationContext applicationContext) {
AppBean = (<Name of class>
applicationContext.getBean("<id of bean in applicationContext.xml");
}
I admit that this is not a great workaround, since you probably want the bean to be injected into the constructor the controller. I think that the proper solution is with the 'ref' attribute in the controller bean specification. Somehow this ref attribute should be able to reference a bean in the applicationContext. If you find the answer let me know.
