How so? The user's selections would be instantly available to the applet. It would not have to check to see what was defined in request space in order to determine which selection was made in which selection box. You would need logic just to find out which box the user selected.
True. But an applet consisting of three combo boxes and a little code would be fairly small.And the user would have to wait for that thing to load.
Yes, but as web sites grow in sophistication (in order, I might add, to meet the growing expectations of users), compounding "browser settings issues" is already pretty much a permanent part of the environment.Also, the age old debate: you compound the user browser settings issues.
That's the whole point. An applet would not need to refresh the entire page just to display new information.And refresh.
Which is easier than debugging JSP? ...on a page that must check the circumstances under which it is being loaded so it can react differently depending on what triggered the (re)load? I really don't think so.And the pain of debugging of the applet.
Absolutely the contrary. Trying to do this with just JSP requires mixing the logic and the view. It is precisely this that the applet would eliminate.And you're mixing logic in your view.
No matter how it is implemented, you have to hit the DB. That is a given.And you still can not make those menus dynamic, unless you hit the DB anyway, so back to square 1. etc.
Too bad. Applets do have their limitations. JSP (and ASP and CFM and ...) have their limitations, also. You should be ready to select the best tool for the job.I have built enough applets to know never to touch one again, if I can help it.
MVC doesn't mean your programmers develop the JSP page and then hand it off to the designers to pretty it up. MVC means the programmers never see a JSP page and the designers never see Java. The only way you can strictly adhere to MVC principles using JSP is to have ALL your code in custom tag handlers. Technically, even "<%= someVar %>" is Java code and should not appear on a page.JSP is the way to go. Code and unit test the logic in <1 hr and then let your web designers deal with colors etc. MVC all the way!
Tomm
____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm
Be respectful! Clean up your posts before replying
____________________________________________________
