RE: Fusedoc-ing Exceptions

[Billy Cravens]

Is that what <assert> is for?   --- Billy Cravens Supercomputer: Turns CPU-bound problem into I/O-bound problem. - Ken Batcher   -----Original Message----- From: Jared Stark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 1:19 PM To: [EMAIL PROTECTED] Subject: Fusedoc-ing Exceptions   This is probably something that has been discussed on the fbsteer list, but since I can barely make it through all my emails as it is I don’t subscribe to it.  I’m wondering about fusedoc-ing exceptions that may be thrown within a template, specifically I mean user defined exceptions.  For example, in my fuses if an attribute is missing I will throw a ‘com.mycompany.attributes.MissingAttributesException’.  I would like to document that somehow so that A) the developer writing the fuse knows about it, and B) a developer using the fuse will know about the exception and can gracefully handle it (hopefully).  I imagine something like:   <exceptions>             <exception type=”com.mycompany.Attributes.MissingAttributeException” onCondition=”A required attribute is missing” comments=”” />             etc… </exceptions>   Has something like this been proposed? How does everyone currently document exceptions?  *Does* anyone currently document exceptions, or am I (yet again) up in the night?   Thanks, Jared ==^================================================================ This email was sent to: [EMAIL PROTECTED]   EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bWapvg Or send an email to: [EMAIL PROTECTED]   T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================ ==^================================================================ This email was sent to: archive@jab.org EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================ This e-mail, facsimile, or letter and any files or attachments transmitted with it contains information that is confidential and privileged. This information is intended only for the use of the individual(s) and entity(ies) to whom it is addressed. If you are the intended recipient, further disclosures are prohibited without proper authorization. If you are not the intended recipient, any disclosure, copying, printing, or use of this information is strictly prohibited and possibly a violation of federal or state law and regulations. If you have received this information in error, please notify Baylor Health Care System immediately at 1-866-402-1661 or via e-mail at [EMAIL PROTECTED] Baylor Health Care System, its subsidiaries, and affiliates hereby claim all applicable privileges related to this information.