Auto-refresh providers

Identifier:
org.eclipse.core.resources.refreshProviders

Since:
3.0

Description:
The workspace supports a mode where changes that occur in the file system are automatically detected and reconciled with the workspace in memory. By default, this is accomplished by creating a monitor that polls the file system and periodically searching for changes. The monitor factories extension point allows clients to create more efficient monitors, typically by hooking into some native file system facility for change callbacks.

Configuration Markup:

<!ELEMENT extension (refreshProvider)>

<!ATTLIST extension

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED

>


<!ELEMENT refreshProvider EMPTY>

<!ATTLIST refreshProvider

name  CDATA #REQUIRED

class CDATA #REQUIRED

>


Examples:
Following is an example of an adapter declaration. This example declares that this plug-in will provide an adapter factory that will adapt objects of type IFile to objects of type MyFile.


   <extension
         id="coolProvider"
         point="org.eclipse.core.resources.refreshProviders">
      <refreshProvider
            name="Cool Refresh Provider"
            class="com.xyz.CoolRefreshProvider">
      </refreshProvider>
   </extension>

API Information:
Refresh provider implementations must subclass the abstract type RefreshProvider in the org.eclipse.core.resources.refresh package. Refresh requests and failures should be forward to the provide IRefreshResult. Clients must also provide an implementation of IRefreshMonitor through which the workspace can request that refresh monitors be uninstalled.

Supplied Implementation:
The org.eclipse.core.resources.win32 fragment provides a native refresh monitor that uses win32 file system notification callbacks. The workspace also supplies a default naive polling-based monitor that can be used for file systems that do not have native refresh callbacks available.


Copyright (c) 2004, 2005 IBM Corporation and others.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html