[OKC JUG] Guidance

[Jason Lee]

Ivan Zhidov wrote:
> Given Jackie's experience I would suggest a low-tech approach of
> creating a simple JSP-based aplication that processes the uploaded file
> using the existing validation logic and presents the user with the
> output text file with listed errors. If no errors were encountered the
> data shall be persisted in the database.

IMO, no should ever use JSP.  Ever.  If Rod Johnson is right and using 
JDBC (directly) should be a sackable offense, using JSP should get you 
night in the iron maiden... :P  On a more serious note, a JSP approach 
will either teach and/or require bad practices, or require much more 
work (IMO) to handle getting the data, processing, doing forwards, etc. 
  Since NetBeans is in the mix, heavy dependence on its wizards, etc. 
should grease the skids a good deal on the framework side.

> The idea is to re-use as much of the existing process as possible and
> deploy it with very little effort. Jetty or Tomcat should be sufficient.

Jetty, though, will require more work to set up, since it is not 
integrated into the IDE.  NetBeans 6 *does*, though, support Tomcat 6, 
something I had forgotten about, so that might be an option, depending 
on what the app is using (i.e., other JEE technologies, which I doubt, 
given what has been said so far).

-- 
Jason Lee, SCJP
Software Architect -- Objectstream, Inc.
Mojarra and Mojarra Scales Dev Team
https://mojarra.dev.java.net
https://scales.dev.java.net
http://blogs.steeplesoft.com