HTTP 500 is a server error, so the error is likely to occur in the server implementation.
If you want to set breakpoints etc, then you should do it in the RESTful service implementation class that is supposed to handle the request (DELETE in your case).
Understood. As stated in my original post I started Glassfish in debug mode and placed breakpoints in my web service application, but everything ran "smoothly" or so it seems. Other than the glaring 500 error there was nothing in NetBeans that indicated an exception had occurred. At least nothing that jumped out at me. I'm a Delphi developer by trade and Delphi
IDE does an excellent job of breaking on exception so you see not only the location of the exception, but what exception was raised and the call stack at that time. I'm not sure if NetBeans has something similar, but anything close to this would be helpful. I was unable to find any debugging options to perform a similar break on exception function. Again, when I reproduced the exception while running Glassfish in debug mode and by setting breakpoints at the appropriate places in my WS app, nothing useful was gained from what I could tell. The flow did stop on the breakpoint as expected, but stepping into, over, etc. all ran as if no exception had been raised. Perhaps I'm just not doing something correctly in NetBeans to debug properly.
Have you had a look in the GlassFish log? Isn't there any exception there?
No. I always forget about the @#$ log! I'll check it out.
Thanks,
Michael