----------------------------------------------------------- New Message on BDOTNET
----------------------------------------------------------- From: geek_prad Message 4 in Discussion I would consider this a high level architectural decision and not to be done at the development stage. The method would vary depending on how your components are communicating between tiers. For instance, many applications use XML as the messaging standard to communicate b/w tiers. In this case, you may need to put an entry into your payload and check for the error number, description etcetera. Another option in .NET would be to serialize the exception object into an XML and then deserialize it at the other end-point. In case you are directly invoking components on diff layers (using remoting or ES), then you may consider using Raghunandan's approach. This is a very standardised approach may applications take. Good luck. cheers, pradeep -----Original Message----- From: BDOTNET [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 4:03 PM To: BDOTNET Subject: Re: Exception handling in 3-tier architecture-Doubt New Message on BDOTNET Exception handling in 3-tier architecture-Doubt Reply Recommend Message 3 in Discussion From: rags_rao use boolean for as return value for update functions. return fasle if there is a failure. and primary key for insert operations (-1 means error). u can also return null if error occurs. for error msg u can throw exceptions (there will a overhead in this method) or return a string or use errMsg as "out string" parameter. its better to keep all the error handling logic in bussiness layer itself. Regards, Raghunandan R View other groups in this category. ----------------------------------------------------------- To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings. http://groups.msn.com/BDotNet/_emailsettings.msnw Need help? If you've forgotten your password, please go to Passport Member Services. http://groups.msn.com/_passportredir.msnw?ppmprop=help For other questions or feedback, go to our Contact Us page. http://groups.msn.com/contact If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list. mailto:[EMAIL PROTECTED]
