An EJB container will generally not give you better performance than a non
EJB container (other than it might be a more efficient...but that will not
be because it is an EJB container). The main difference is that you will be
able to use EJB's and the other Java EE goodies that a J2EE container
pr
Gecko? ;)
My advice: stay away from EJBs as much as you can. They are too complicated
and too heavy for most systems. Servlet containers like Jetty, Tomcat, or
Resin are often perfectly suitable for the job and a lot simpler.
Otis
- Original Message
From: "Chenini, Mohamed " <[EMAIL
I think a standalone J2EE application will be good and better loose
coupling than EJB. You can seperate memory, disk, and CPU resources
from your main application. You can send results back in XML, JSON, or
other formats.
Chris Lu
-
Instant Full-Text Search On Any Database
IN THEORY, EJB containers are better able than Tomcat to spread
incoming requests over a multitude of servers. There was considerable
discussion some time ago about index search speed on a single
processor. I do not remember the details, but there was some
information about how fast a search
EJB explicitly precludes you from accessing files, including via third party
libraries such as Lucene.
http://java.sun.com/blueprints/qanda/ejb_tier/restrictions.html
In practice you may be able to get away with it but I see no particular reasons
why using an EJB server should offer any benefit
