In the context of "web app," Java EE usually means Servlets or JSPs (which are just parts of the EE API). Basically, these allow for server-side programming: The app runs on the server, and generates output for the web client.
But to answer your question, I think you need to tell us more about this web app, and what exactly you expect to get from Java EE.
"We're kind of on the level of crossword puzzle writers... And no one ever goes to them and gives them an award." ~Joe Strummer sscce.org
Joined: Jun 24, 2006
this will be a shopping cart hosted by our server. there will be thousands of users log in potentially.
because I never deployed before, neither configured servets although I know enough code in java, jsp and servlets, I thought Java EE can simplify what I don't know and connect to the server easily. am I right?
If you are using Servlets and/or JSP, *you are already using* Java EE.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by jenny brad: this will be a shopping cart hosted by our server. there will be thousands of users log in potentially.
because I never deployed before, neither configured servets although I know enough code in java, jsp and servlets, I thought Java EE can simplify what I don't know and connect to the server easily. am I right? ...
Servlets (and JSPs) run on the server, so I'm not sure what you mean about using EE to help connect to the server. Can you be more specific about what you're looking for -- what exactly you want EE to do for you?
(Note: You might want to reference a book like Core Servlets and JavaServer Pages, Vol. 1: Core Technologies, Second Edition by Marty Hall and Larry Brown. The older first edition is available free online from the author's site, coreservlets.com. Also, depending on what your situation is, you might consider purchasing a shopping cart application to use -- at least as an interim solution.)
Who lets a programmer who's never created a servlet/JSP application before (and doesn't even know what tools to use apparently) create an entire shopping cart system for a medium volume website?
If I were you I'd turn down that project and start on something less critical to learn the ropes, better for the company/customer and for you as well.
Servlet and JSP APIs are both part of the J2EE platform. You really want to learn how to use them properly though before writing production systems in them, or you're going to fall into all the dozens or hundreds of pitfalls that have plagued early applications and have since been solved through blood, sweat, and tears by those who went before you over the last 7 years or so.
To start with you should look at frameworks like Spring to help you with a lot of the work. Hibernate to do some more. Ready made shopping cart systems are available for purchase from many vendors, why reinvent the wheel when others have worked out the bugs over months or years of effort? etc. etc. etc.