Hello, I was using HTTP services for quite some time and I'm not very happy with the way I handle the server side errors. I was wondering if you have a better idea that you can share with me.
Here are the solutions I used: 1. check exception on the server side and return a XML representation of the error ( message, code ). I kinda don't like this approach, because SPRING does a nice job uncheking all the exceptions and adding back the exception check seems odd to me. I'm looking into adding a java interceptor using AOP, still working on it... 2. Presented a generic error message on the UI - coded onFault method of the HTTP server. This is not ideal, our users will like to see much more specific messages related with the backend error, somehow onFault method seems unusable due to Flashplayer limitations. I was looking into "useProxy" config of the HTTP service but didn't see anything that might help me. Am I missing something? Can you share with me how did you handle the server side errors on the UI side? Forgot to mention that I'm not using FDS, I use the Flex framework with HTTP services ( xml over http ). Thanks, Valy Sivec ____________________________________________________________________________________ Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather
