Thursday, September 5, 2002 08:58 AM
Will the user be accessing the app through a Web browser? Or via a full-on Java application running on the desktop?
If users have a client Java app, then Tomcat probably has no place in this, since Tomcat is a JSP/Servlet container meant to send responses to Web browser http requests. And if Java code on the client is communicating with Java code on the servlet then you should probably check out Enterprise JavaBeans. In any case I would suggest keeping the SQL in the JavaBeans in the middle tier, and not putting it into client code!
If, on the other hand, users will access the app via a Web browser, then Tomcat will serve the JSP pages and execute the servlets.