I'm trying to implement a fairly generic way to handle errors when then occur on the server-side, and then have a uniform way to display some-sort of context on the client. Is there any best practices that you folks know of in relation?
All I can think of is that I have to create a top-level response object, which can contain error information or the real entity/payload that I care about. Or perhaps I can just have an error entity that only gets pushed back when an error occurs and have the client check for it before it tries to pull out the desired entity? Something like that... I dunno, so if you guys know of a better way to handle this I would be very helpful. Would have liked to see some examples of this in the distribution too. IMO, the current examples don't provide enough client <-> server details... lots of atom/rss-ish stuff, which I personally don't care about atm. Overall, I'm trying to get enough insight so that I can write an enunciate module to generate a java client to interact with server resources... as the client-code to request muck is highly boilerplate-ish. Any insight would be very helpful... and some richer wink-examples/** would be even better, but I'd settle for either ;-) --jason
