need advice on a web based project development

[orhie]

hi all,

First things first, I am quite new to java and related stuff war, ejb, jsp etc.

Im trying to design an application which will
-be accessed by a web browser
-will store all the data on a DB (mysql is what im thinking)
-will have user login (each user will have different access levels)
-min 500 people will be online at all times
-the DB will host more than 5million records
-the db will be like cars, licenses, drivers, penalties (not mentioning user, user groups, etc)

how will the software work:
user logs in using: username pass accountid
according to user-rights(access level) the thing he/she can to will be shown in first screen
user will chose an option and the next page will be shown with options again according to users access-level
when editing updating inserting a record the user will enter a secondary password to confirm the action


and dont know why but i have a thing for security so i want the system to be as safe and stable as possible
by the way i dont have hardware problems so if using the method you advised requires alot of cpu power no problem

well i hope the car driver example brought an image to you guys

well my problem is i dont know what to use when coding:
ex: login page can be html(login page)-->jsp(user-pass verification) or jsp(login page)-->jsp(will check login true javaclass)--> java class

i want to use java and java based systems, please help me i dont know what to choose war, ejb, jsp-java, jsp-html, etcc

thanks a bunch in advance

yours,
orhie

[Tolls]

HTML (or JSP, depending on how complicated your front page is, ie other information that might be drawn in from elsewhere) to a Servlet (or Action/Controller if using Struts/Spring), which will do the checks and forward to either a login failed jsp or the "normal" success jsp.

Start out correctly...do not put business logic in JSPs. They are for displaying data.

[orhie]

thanks for the reply tolls
well the design is important but i believe jsp can be enough but other than that u r saying use jsp to deliver the data from and to client like jsp--->java( he work is done here)--->jsp(result) ??

[Tolls]

Look at almost any question on here or the Sun/Oracle forums where someone has put non-display code into a JSP page and you'll see them being told to move that code out.

It also makes it possible to test in isolation, which is very important.

HTML is fine if the page is static. Otherwise a JSP page is probably needed. So if the login page is static then HTML will be fine.

That givew the flow:

request from login.html --> login servlet (calls authentication code) --> forwards to relevant JSP --> back to client

[orhie]

there is one more thing i wanna ask
if i create the app like
html--->jsp-->> java class-->jsp-->html
im usiing html for the ease of design :) layz me :D will it have any negative effects on my security and is it possible to do it in 5 steps as i wrote or shorterr

[Tolls]

No problem with an plain html login form.
You can do the login logic straight in a JSP page, avoiding both a servlet and any java beans, but that's even worse than your plan to avoid a Servlet.

Avoiding using a Servlet is not being lazy. You will discover the "joys" of debugging a JSP with your current plan, which will take you far longer to resolve any bugs than writing a simple servlet.

[Armadillo]

Actually, depending on how complicated your user interaction is, you may want to use a framework to deliever the data to the user. For example Apache Wicket - Welcome to Apache Wicket.
Your stuff will still all be in java, and your business logic will bein plain, testable, java classes but it makes it easier to write the front end components because you can use and extend the components from the framework.