All,
we've noticed that implementations of
org.opennms.api.integration.ticketing.Plugin don't have a way of
telling the service layer that a get, save or update has failed. 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.
Cheers ... J
-------------------------------------------------------------------------
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
