[
https://issues.apache.org/jira/browse/AXIS2-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishanthan Thangarajah updated AXIS2-5231:
------------------------------------------
Attachment: deploy_multiple_spring_services.patch
With this patch, the users do not have to initialize spring by implementing
ServiceLifeCycle class and running it on start-up. Spring context
initialization is moved inside spring module. I have introduced a util class
which will supply the applicationContext on when the service in invoked. This
will also remove the need for the ApplicationContextHolder class.
> Cannot deploy multiple spring service axis2 archives within a single axis2
> instance
> -----------------------------------------------------------------------------------
>
> Key: AXIS2-5231
> URL: https://issues.apache.org/jira/browse/AXIS2-5231
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.6.1
> Reporter: Kishanthan Thangarajah
> Fix For: 1.7.0
>
> Attachments: deploy_multiple_spring_services.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
