I believe it's a trade-off - I'd say there are likely very few systems can be built using EJB technology that couldn't be built using JSP/Servlets as well. Here are a few things to think about:
- Generally using EJB the container provides various services (e.g. transactional management, security, etc.). While there still may be requirements to provide some supporting code for these services, the overall amount required may be less. In addition, the state of these services is likely to be easier to communicate among components as well. - Using EJB's can make it easier to enforce good OO design principles and make the JSP that remains better. One of the knock's against JSP is that programmers have a tendency to code business logic (or data access, transaction mgmt, etc.) directly into the JSP page rather than abstract it into some other component. Using EJB's will likely reduce this tendancy and push non-presentation logic into the components. In fact, just the act of thinking through how to design EJB's during the architectural design portion of a project will generally result in code that has a better design and is more maintainable (that is, costs less to maintain). - EJB's actually do promote component reuse among projects. I've seen it happen where someone takes an EJB and adds (or generalizes) some functionality and makes is useful on another project. (Again, component reuse promotes lowering the cost of later projects). - Handling data through well-designed entity beans can minimize the number of developers that need to know sql/JDBC. Developers end up using Business Objects, versus database tables - which promotes ease of maintenance and better design. (keeping programmer productivity higher and reducing cost) - Having a single app server for all projects (ejb or not) reduces overall learning curve and development time. This allows you to apply the right tools for the job (EJB or JSP) while not having multiple platforms to develop on. On the other hand, EJB containers (except JBOSS and other open source) are generally expensive. All have a learning curve. In the end it's a long-term decision on an overall platform to use to solve the business' problems. I say choose a good app server and let the business problem dictate the approach (EJB -v- JSP). Don't just choose JSP to solve every problem because it's all you know or all you have. __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
