Re: Why JavaEE / EJB3?
- From: Alex Hunsley <lard@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 11:41:30 +0100
Marc E wrote:
Greetings all,Hi Marc
For a current project, I'm trying to decide whether to stick with how we've always done it or whether to invest the time, energy, and resources into making it a full J2EE app. I've never worked with ejb, jms, etc before.
The "way we've always done it" is Tomcat/jsp/jstl/pojo. No servlets, no MVC, no need for multiple clients (swing vs. html vs. mini devices), no need for internationalization. just straight up database (via jndi and datasource setup in server.xml) and html (ala jsp).
a book I recommend to people asking themselves this question:
"J2EE Design and Development, Expert one-on-one", Rod Johnson, published by Wrox Press Ltd.
Early on he covers good reason to use, or not to use, J2EE solutions.
lex
.
- Follow-Ups:
- Re: Why JavaEE / EJB3?
- From: Marc E
- Re: Why JavaEE / EJB3?
- References:
- Why JavaEE / EJB3?
- From: Marc E
- Why JavaEE / EJB3?
- Prev by Date: Related to Performace of URLConnection.getOutputStream
- Next by Date: Re: ws-addressing WSDL binding
- Previous by thread: Why JavaEE / EJB3?
- Next by thread: Re: Why JavaEE / EJB3?
- Index(es):
Relevant Pages
|