[
https://issues.apache.org/jira/browse/AXIS2-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192994#comment-13192994
]
Kishanthan Thangarajah commented on AXIS2-5231:
-----------------------------------------------
Hi,
I have posted a blog post[1] based on the above recent improvements. Also
included a sample.
Thanks,
[1]
http://kishanthan.wordpress.com/2012/01/25/how-to-deploy-multiple-spring-service-axis2-archive-aar-within-a-single-axis2-instance/
> 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,
> deploy_multiple_spring_services_V2.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: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
