I think it's not so obvious. Generally you say that user exceptions should not be printed to log. But how can you distinguish between user thrown WebApplicationException and Wink thrown such an exception?
In addition I think that there are users, who would like to know if their code throws an exception, since it indicates a problem, an the only place that can catch and log it is Wink (yes, there are at least two other options: implement a handlers or implement an ExceptionMapper, but I think that user expects logging out of the box). The compromise can be sending the stacktrace to log only at debug level. On Fri, Dec 11, 2009 at 11:42 PM, Nicholas L Gallardo <[email protected]>wrote: > +1 > > User exceptions shouldn't be logged given that they may be a normal part of > the exchange. > > > > Nicholas Gallardo > WebSphere - REST & WebServices Development > [email protected] > Phone: 512-286-6258 > Building: 903 / 5G-016 > > [image: Inactive hide details for Bryant Luk ---12/11/2009 03:37:26 PM---As > mentioned by djna on wink-user regarding the exception logg]Bryant Luk > ---12/11/2009 03:37:26 PM---As mentioned by djna on wink-user regarding the > exception logging, > > > *Bryant Luk <[email protected]>* > > 12/11/2009 03:36 PM > Please respond to > [email protected] > > > To > > [email protected] > cc > > > Subject > > Change to logging exceptions > > As mentioned by djna on wink-user regarding the exception logging, > there is a lot of logging going on if an exception is thrown from a > resource method (which can happen multiple times and is expected for > whatever reason). I think the request to reduce the logging is > reasonable and I'll change the logging behavior in the trunk later > unless someone has an objection. > >
