Comments for The Quest for Great Software

Comment on How to Migrate a Legacy EJB Application to Spring and Hibernate by camestres.com » Links for 11/5/2010

camestres.com » Links for 11/5/2010 — Tue, 11 May 2010 16:19:37 +0000

[...] How to Migrate a Legacy EJB Application to Spring and Hibernate « The Quest for Great Software – [...]

Comment on When Writing Developer Tests, Take on Account that the JRE Is Another Leaky Abstraction by Eugene

Eugene — Wed, 22 Oct 2008 23:34:34 +0000

Nice article. Thanks. Eugene

Comment on How to Migrate a Legacy EJB Application to Spring and Hibernate by Timo Rantalaiho

Timo Rantalaiho — Mon, 22 Sep 2008 04:51:06 +0000

Hello jaimex,

Nothing especial about that. The DataSource bean can be changed to look up a WebLogic-managed DataSource from JNDI instead, though the current version is good to have for development too, so that you can develop without having to have WLS running.

There’s no interesting state on the application as it is, so I’m not sure what you’re after with regards to clustering. If you add something that uses HTTP sessions, failover and session replication (if you really really want it) can be configured normally. It doesn’t really depend on the backend.

Best wishes,
Timo

Comment on How to Migrate a Legacy EJB Application to Spring and Hibernate by jaimex

jaimex — Thu, 18 Sep 2008 14:06:24 +0000

How could I deploy this in an application server such as weblogic in order to cluster it?

Comment on Why Migrate a Legacy EJB Application to Spring and Hibernate by Timo Rantalaiho

Timo Rantalaiho — Wed, 28 Nov 2007 04:18:05 +0000

Hi Muthu, the other article is right there

http://kaksles.org/2007/08/11/how-to-migrate-a-legacy-ejb-application-to-spring-and-hibernate/

after this one. It’s really more of an example than a full-blown guide, but I hope you’ll find it useful!

Comment on Why Migrate a Legacy EJB Application to Spring and Hibernate by Muthukumaran

Muthukumaran — Wed, 28 Nov 2007 03:59:33 +0000

Hi,

Nice artical, i am looking for the handson guide to conver exesting EJB application to Spring & hibernate.

We are looking at migerating our exesting application to Spring & Hibernate, please let me know when your guide is ready. I will be of great use to us

Thanks,
Muthu

Comment on When Writing Developer Tests, Take on Account that the JRE Is Another Leaky Abstraction by Markus Hjort

Markus Hjort — Sun, 26 Aug 2007 12:13:45 +0000

I guess Ville proposed this idea because we used to use different JRE for our unit tests in our last project. JRE 6.0 was used for tests, while production server was JRE 1.4.2. Although, we had different JRE for unit tests, we did run all higher level tests with same JRE as used in production. So we actually had three different modules: for production code, for unit tests and for integration tests. I know that it is a bit complex setup, but for us it worked pretty well.

And I totally agree with your point. Project’s continuous integration environment should be very similar with production environment. So you should use same JRE if it is possible.