Juraj Kazda wrote:
> There is model written down in J2EE, where user calls JSP or servlet,
> JSP/servlet calls EJB, EJB returns results to JSP/servlet and then output is
> generated back to user. For what situations is this good way? Isn't it
> enough to do all backend operation just in JSP/servlet? Should I use EJBs?
EJB gives you a distributed transactional framework in which much of the "hard"
work has already been done for you. All you need to do is implement your
business logic.
You could most certainly implement these things yourself, but why reinvent the
wheel?
One could ask the same question about application servers - why use them? Well,
they too perform many non-business related functions that are necessary like
session management and connection pooling.
I think that the trend of bundling app servers with EJB servers will become
stronger and stronger as these technology vendors (open source included) try to
provide the very best solution that they can. Even enhydra and jonas now have an
alliance.
--shawn
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
