> On 2025 Aug 14, at 16:42, Daniel Schwartz <d...@danielgschwartz.com> wrote: > > Please see the reply is just sent to Chris. I think that this answers your > questions. > > I don't know why people thought I was using servlets.
Likely because both Tomcat and GlassFish are servlet containers, and you were asking questions on the Tomcat mailing list. In actuality, you are using servlets, but under the covers. The GlassFish implementation of RESTful services wraps your application code in servlets. > It's a REST web service. I thought that this was clear. REST web services are often implemented as servlets, so REST does not preclude your use of servlets. > My code currently catches SQL exceptions, and prints out an error message > when/if it gets one; and if some other type of exception is thrown, the JVM > will output a stack trace and terminate. This is a misconception on your part. GlassFish is a complex beast, with many threads capable of handling multiple concurrent requests, DB connections, and all the associated management thereof. An exception in application code (your RESTful web service) would only cause that request to be aborted - it would not shut down the JVM (unless something is seriously broken or badly misconfigured in GlassFish). - Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
