Interesting, please let me know your results! Anybody else here doing something similar?
-J On Tue, Mar 4, 2008 at 10:31 AM, Tracy Spratt <[EMAIL PROTECTED]> wrote: > I am just getting started with webservices, using .net, so this is just > talk. > > > > Kinda like I do when I use HTTPService, I am experimenting with a > standardized error/exception xml structure I return when there is any > handled problem on the server. In my result handler, I test the root node > for a known name(), like "<ERROR>" and handle the result accordingly. > > > > Now, I am also experimenting with the strongly typed results from the FB3 > generated code, and have not reached a point where I have integrated my > Error node with that code. Interesting. > > > > Tracy > > > ------------------------------ > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *Josh McDonald > *Sent:* Monday, March 03, 2008 7:07 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] Web services: Patterns for recoverable errors like > business rule violations? > > > > Hi Guys, > > Are there any good patterns for recoverable errors? I mean when > communication with the server is working a-ok, but you need to let the user > know they've violated a business rule or something along those lines, and > they need to rethink their behaviour :) > > How are you handling this sort of problem? A specific kind of fail, or a > funky result packet that your DAOs are aware of? > > -Josh > > -- > "Therefore, send not to know For whom the bell tolls, It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] > > -- "Therefore, send not to know For whom the bell tolls, It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
