[AXIS2-5231] Cannot deploy multiple spring service axis2 archives within a single axis2 instance

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.1
• Fix Version/s: 1.7.0
• Assignee: Kishanthan Thangarajah
• Reporter: Kishanthan Thangarajah
• Created: 12/Jan/12 06:13
• Updated: 20/Feb/12 07:46
• Resolved: 13/Jan/12 11:30

Description

Current issue with adding multiple spring service is that when we add a second service, the first one does not work or rather the deployment of the second service breaks the first. This is because of the static nature of spring ApplicationContext variable in ApplicationContextHolder class. Current way of initializing spring framework for a service via a service class which implements the ServiceLifeCycle interface. In this method only, the spring application context is created with the applicationContext.xml file. The beans defined in the context file will be defined in this context and the context will be set to the static ApplicationContext variable of the ApplicationContextHolder class. When a second service deployed the same operations mentioned above will happen and finally the spring ApplicationContext of the first service will get replaced by the second service's ApplicationContext. So if you invoke the second service it works, but when invoking the first service, it gives an error as no defined beans are found.