I'm not sure what benefit we get from this. We already give the errors returned to the client a status code. On the server side, they are all printed with stack traces which make it much easier than any error code to. We also don't want to swallow the exceptions thrown by third-party libraries since you can search for those in Google or Bing.
Where are you specifically looking for error codes? Thanks Scott On Tue, Dec 14, 2010 at 8:32 AM, Yuri Negocio Negocio <[email protected]>wrote: > Scott, > > What do you think of standardizing the errors introduced by the CAS based > on a similar numbering to databases (Oracle, PostgreSQL). > > Example: > > CAS-0001: Invalid configuration ... > > From this standardization could work to describe the error and a possible > solution to the problem, similar to StackOverflow. > > This is a common request of my infrastructure team. > > Cheers, > > Yuri > > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
