Nic,
You are right, there is not perfect solution. But let us try to find the
better.
Let me tell you a little about the cost. There are several free J2EE servers
available (and also you can get the source code for some of them if you want
to play with it). The hardware requirements are not much different from a
JSP/servlet engine for the same application.
Also, if you do not use a J2EE server and decide to write some of the
features of the J2EE server like transaction management, security, database
connection pooling, life cycle management, etc. you are spending more money
on development time and also on maintenance time.
Benjamin
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 14, 2001 4:18 PM
To: [EMAIL PROTECTED]
Subject: Re: Differences between serlets/jsp and ejb
>>> "Nevarez, Benjamin" <[EMAIL PROTECTED]> 14-May-01
11:32:43 PM >>>
>Sun recommends several components for different
>kind of applications:
>1. Basic JSP and servlets
>2. JSP Pages with modular components (servlets,
> JavaBeans or custom tags)
>3. JSP Pages with modular components and EJBs
> (same as before plus EJBs)
>As you go from 1 to 3 there is an increment in Complexity
>but also in Robustness.
So they say. Robustness is hard to measure. Though I certainly can
measure the cost in dollars of moving from 2 to 3 /8->
Sun technologies aren't the only way to deal with this stuff... I've
got a lot of time for things like Cocoon which IMHO make the
separation of code and display much clearer than JSP ever does.
>Can you imagine a web designer working with complex
>servlets to change the user interface? You can for example
>just update the presentation, in this case JSPs, without
>modifying the controller or the business rules.
Yes. But you can do all of that without using EJBs. EJBs don't
provide anything in terms of clarifying program structure - IMHO they
muddy the water with the need for several different objects to
represent a single entity.
What you get with EJBs can actually be a lot clearer with a well
designed object API.
What I'm trying to get over here is that it's bad to be slavish to
the latest thing. The EJB paradigm has advantages... but it has
disadvantages too and it's not the only option for scalability and
robustness.
In my view EJBs are an excellent way of building an app really
quickly. Probably faster than you could build it any other way. But
there is a cost associated with the dynamism and it's a cost you can
reduce by rebuilding outside of the EJB environment.
Nic
___________________________________________________________________________
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
___________________________________________________________________________
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
