Re: [opennms-devel] change to ticketer api - comments please

On Nov 7, 2008, at 2:35 PM, jonathan sartin wrote:

> This results from communications failure with the remote ticketing  
> system and can leave the alarm in a incorrect state. I intend to add  
> an exception to the Plugin interface that can be thrown if the  
> remote connection fails. That way, the service layer can catch the  
> exception and abandon updates to the alarm.
>
> What do you think? Let me know if I've missed something.

After thinking about this a while, I wonder if adding a few more  
ticket states for which the service layer could check would be in  
order.  Such as CREATE_FAILED/UPDATE_FAILED/CLOSE_FAILED states.  Each  
of these could generate events->alarms.  What do you think?


David Hustace
The OpenNMS Group, Inc.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel