one Question I have about JSP files: Are they old fashioned today as some people say or is this only one opinion from many others ?
Web apps tend to start with JSP files. I don't know what you mean by old fashioned; it does support a lot of syntax which is currently not recommended.
If you write clean tags with expression language (EL) and libraries (JSTL), it works fine.
If you're starting a clean new app, I think you can avoid JSP. JSP files can call other code, other code doesn't do so well calling JSP files, so maybe unavoidable working with an existing app already full of JSPs.
JSP is all back end. There's a pre-process that turns it into a .java file when the servlet gets a request for it. That Java program runs all back end code first (you can write Java code in a JSP file using scriptlets but there is a better way now). Then
it kicks off any in-line Javascript code. Then it sends any html code to the front end and loads that. If you want to do back end code before the JSP loads and avoid the scriptlets, you can save the JSP file somewhere other than the default web path,
catch the requests with a servlet, set pass values using EL, then forward the request to the JSP file.
It is probably best to avoid JSP files if nothing in the app is forcing the use of them. If you can write them clean, they're basically fancy HTML, but can still be harder to debug.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)