Resource modification hooks

Most of the interesting function associated with a repository provider occurs as the user works with resources in the project that is configured for the provider.  In order to be aware of changes the user makes to a resource, the provider can implement resource modification hooks.  The resources plug-in provides these hooks as extension points.  The documentation for IMoveDeleteHook and IFileModificationValidator describe the details for implementing these hooks.

The team plug-in optimizes and simplifies the association of the hook with appropriate resources by registering generic hooks with the resources plug-in.  These generic hooks simply look up the repository provider for a given resource and obtain its hook.  This has the advantage of calling only one provider hook rather than having each provider implementation register a hook that must first check whether the resource is managed by the provider.

What this means to your plug-in is that you provide any necessary hooks by overriding methods in RepositoryProviderThe default implementation of these methods answers null, indicating that no hook is necessary.

Copyright IBM Corporation and others 2000, 2003.