On 10 Nov 2008, at 18:41, jonathan sartin wrote:

>
> On 10 Nov 2008, at 03:10, David Hustace wrote:
>>
>> 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?
>>
>
> I think that this is a good idea. If we did this, then we could make
> the service layer responsible for dealing with failed updates. Removes
> my plugins dependence on opennms-services, which is a good thing. I'll
> do that.

So I've made some progress on this in the feature-ticketing- 
improvements branch of opennms and platform. The OTRS ticketer no  
longer depends on opennms services as I've moved that dependency up  
into the DefaultTicketerServiceLayer. I'm about to start on the RT  
plugin and I wonder if it's time to move all the ticketer plugins out  
of the core of opennms. I seem to recall that  Ben was going to do  
this at DevJam but was thwarted by the OTRS ticketer plugin dependency  
on opennms-services.

The question is, where should it go? Do we want to create a new  
"package" such as "opennms-plugins" and put all the ticketer plugins  
in there, or should they go in platform?

I'm not blocked on a decision, but I'd like to get this sorted for the  
next release.

Cheers ... Jonathan.

-------------------------------------------------------------------------
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

Reply via email to