hi everybody,
currently we are using servlets and JSPs for our websites (running on apache
with jserv) and I have to say we are pretty satisfied with that technology:
we are using handy utility classes (for database connection pooling, db-date
retrieving, and so on) which make our lifes easy
but i have to say our websites are pretty easy (product catalogs, small
shopping malls for small companies...) and low-traffic, but soon we could do
projects with
a) more functionality and
b) more traffic
often when i read success-stories of e-portals or related things, many
authors say they are using J2EE-compliant Application Servers such as
Weblogic, Websphere and so on
So, my question is:
- are these appservers choosen because of their advantages like built-in
jsp/servlet-capability, db-pooling, stable http-servers, add-ons like ssl
and so on
- or are they explicitly choosen because using EJB is a MUST today?
Who would recommend using EJBs (additional or instead our database-access
and other tools classes), and if so, under which circumstances and why ---
or: when would you say EJBs are contraproductive (performance problems?
buggy ejb container?...)
Should we switch completly to EJB, or only for projects of a special
complexity?
- I really would do my first EJB-project as soon as possible, but I fear its
very risky, so I ask people who have experience on this topic and/or who
have a certain overview over the web-industry and the technology it uses!!
it would be great to hear your opinion!
Joe Peer
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
