It's not a secret anymore!
The moose likes EJB and other Java EE Technologies and the fly likes EJBs and legacy systems Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJBs and legacy systems" Watch "EJBs and legacy systems" New topic

EJBs and legacy systems

Thad Humphries

Joined: Feb 04, 2011
Posts: 20

Can you give me some philosophy on EJB vs non-EJB solutions to interfacing with legacy systems? A few years back, we were given the job of writing a web interface to a system where the database, business logic, etc was already established with a well defined C API (and used by several non-Java clients). The team's decision was to go for a simple servlet & JSP solution on the idea that a EJB solution would involve a lot of overhead. With the business logic already set, it seemed the right move then, and it seems right now as an Ajax interface has replaced the JSPs. However I wonder what we might have missed by not using EJBs (aside from another set of initials on our resumes).

Can you give me some cases where EJBs coexist with an existing system? What should we look for when faced with this again?

"Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, Doctor Faustus (v, 121-24)
Richard Reese
Ranch Hand

Joined: Jul 13, 2011
Posts: 84


I don't have experience with that. However, the following might help:

Richard Reese
Java 8 New Features: A Practical Heads-Up Guide
It is sorta covered in the JavaRanch Style Guide.
subject: EJBs and legacy systems
jQuery in Action, 3rd edition