We currently have an application running on Spring 2.5.6 (Spring MVC, Spring core, Spring JDBC and Spring AOP). This application is deployed in Websphere 6.1 . There is now a plan to upgrade the server into Websphere 7.0 or if possible, Websphere 8.0.
I understand that since Spring 2.5.6 is compatible with Java EE 5, it will have no problem if the server is migrated to Websphere 7.0. Is my understanding correct?
I cant seem to find any resource in the net saying if this version of Spring would work in Websphere 8. Can anyone answer this? I'd appreciate any form of help.
Spring Framework is never dependent on a specific App Service, Web Container, StandAlone or UnitTest, it is always the same, works the same. So there is no difference if you deploy it on Tomcat 6.x, Tomcat 7.x, WebLogic 10, WebSphere 7.0, WebSphere 8.0, a Swing application.
We are using spring 2.5.6 with WAS 6.1, it works fine but same code is having issues with WAS 7.0 while deploying. We keep getting the below error in system out logs. Appreciate any insight.
org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'service1': Bean with name 'service1' has been injected into other beans [serviceDAO1] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.
We also tried setting lazy-init="true" but keep getting the same error.