I think you may be comparing apples and oranges a little
bit here. Two problems with using a pure "Servlet to database"
architecture is with synchonization and massive database
hits. For smaller apps, this is probably fine, but for
larger ones you can run into problems with improper
record locking and poor database performance. EJBs help
administer the middle ground between "front end" java (whether
in the form of servlets, jsp, java apps, applets, or
whatever) and the database. There are many other
advantages to using an EJB architecture like having better
seperation of code modules and faster development
schedules, but that's a whole other discussion. As far
as security, good question. I don't think so, but then
I have no technical arguments to support that assertion.
I'm sure some others may.
Frank
-----Original Message-----
From: Mantri, Mr. Ramesh [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 12:48 PM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] RE: servlets vs. EJB
All,
That is an interesting question. I prefer to use a mix
of both. In my opinion, servlets are easier to develop
than EJB. But then I am almost a newbie and could well
be wrong. There is an important problem with EJB, I
think. It seems to require a wide range of ports to be
available for communication. That could pose a serious
challenge to Network Security. What do the experts think?
sincerely,
Ramesh
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
