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)