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.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
==^================================================================

Reply via email to