Alex

We don't want to have any of these methods to have `throws *Exception`. What that does is pass the exception back up (or down, however you see it) the call stack. So that would mean that the Web is the next thing to see it. Basically we just want to decide what happens if an error happens in the service layer, since that's the logic layer. So you should get rid of the throws in the declaration and throw a try/catch into the method and handle that error. You'll probably want to log it (with System.out.println()) and then return either null or Response.Status.ERROR or something like that. 

Side note, for these methods that return void, we want to return a Response.Status so that we see on the client how our request was handled and if we need to let the user know to try again