Matt, When you send a HTTP error response you can include an XML body as well. So you get the best of both worlds.
Paul On 22-Jan-09, at 10:32 AM, [email protected] wrote: > Hi Paul > > Thanks for the advice. You can easily to the 'content type' with the > TunnelService and it works just fabulous. I got that. We are not > 100% if we are going to use WADL and I think they is some TOS > requirement to be in every response. That was the entire 'wrapper' > things. Also. As far as errors go there was a desire to have it in > the xml if the error was say a missing param or or something. The > desire was to have something like > > <errors> > <error> > <code>999</code> > <message>start date is before end date</message> > </error> > </errors> > > There was totally some desire to have the easiest and most verbose > way to manage errors for the user as these 'restful' requests are > going to have many many many optional params and some might conflict > with eachother so the messages have to have some easy and quick > visual rep to the user. This is not my ideal but I am not writing > the recs. I will look into returning http error response as well! > > Thanks for the advice. > > matt > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1043422 Paul Austin President/CEO Revolution Systems Inc. +1 (604) 288-4304 x201 www.revolsys.com ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1044878
