Posted by Johannes Nicolai on December 21, 2011
One major feedback we received on CCF 1.x was that our customers really liked its bidirectional artifact synching functionality to HP ALM/Quality and Scrumworks Pro but did not like the fact that they could only control its behavior from a locally installed Eclipse client. As part of CollabNet’s Connect Initiative, we started over with TeamForge [...]
Categories: Application Lifecycle Management (ALM), CollabNet TeamForge, Community Management
| 
Tags: automation, CCF, CollabNet Connect, Eclipse, Hospital Entry, HP ALM, HP QC, Python, remote access, Reporting, REST, scripting, scrumworks, synchronization, TeamForge, Visual Studio
| 
View Comments
Posted by Johannes Nicolai on August 2, 2011
TeamForge’s custom event handling framework implements an extended flavor of the observer pattern. It allows third party event handlers to register for TeamForge specifi c application events and will notify them whenever such an event occurs. TeamForge application events are triggered whenever a property of a TeamForge object (e.g. tracker item, discussion item, wiki page) has been changed or is going to be changed if no event handler objects (i. e. blocks the event).
The framework di fferentiates two diff erent types of events: If a handler registers for asynchronous events, it is informed that a change had just happened. The handler can decide to trigger further changes by calling TeamForge web services, but it cannot block the change because it has already happened. If a handler has registered for synchronous events it gets informed whenever a change has been anticipated by a user.
In this blog post you will learn
* How custom event handlers interact with TeamForge
* How to write your own custom event handlers (including best practices)
* How to benefit from custom event handlers without having to write a single line of Java
* How to avoid common pitfalls in event handler design
* How to trouble shoot your event handlers
* How you can help us improving our existing documentation on event handlers
Categories: Application Lifecycle Management (ALM), CollabNet TeamForge
| View Comments
Posted by Johannes Nicolai on July 15, 2008
One of our main goals and success factors at CollabNet is to listen carefully to our customers and prospects to understand your specific requirements. These requirements drive the development of new features within our products significantly. This blog post is a call for participation with two opportunities – An opportunity for us to listen to [...]
Categories: Uncategorized
| View Comments
