• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Spring 2.5.6 on Websphere 7.0 and Websphere 8.0

 
Ranch Hand
Posts: 178
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Greetings,

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.



Thanks and good day to everyone,
Andres

 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Spring Framework is never dependent on a specific App Service, Web Container, StandAlone or Unit Test, 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.

Mark
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Mark,

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.

Regards,
Sat
 
Mark Spritzler
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Remove the circular reference. That is a code smell anyway. One class being dependent on another that is dependent on the first class is a bad design.

So, Spring actually doesn't have the problem, it is working. It might be WebSphere JTA TX Manager that has the problem.

Anyway, get rid of the circular reference and it will clean it up.

Mark
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic