List of synchronize() Examples

Examples of synchronize()

clips.delegate.directory.complex.DirectoryMKB10.synchronize()
com.esri.gpt.agp.sync.AgpPush.synchronize()
Execute the synchronization process. @throws Exception if an exception occurs
com.moesol.geoserver.sync.client.GeoserverClientSynchronizer.synchronize()
Try to synchronize with the server. This method either succeeds or throws an IOException. @param features Map of feature id to object that is read to determine what client already has.The feature listener is called to notify clients what operations are needed to update the features. Note that the default feature listener will put/remove features to make it match the server. @throws IOException @throws ParserConfigurationException if provided configuration has an issue @throws SAXException
com.sun.enterprise.ee.synchronization.SynchronizationDriver.synchronize()
Attempts to synchronize the client (server instance, node agent) with the central repository. @throws SynchronizationException if an error occurred during the synchronization process
com.sun.enterprise.ee.synchronization.api.ApplicationsMgr.synchronize()
Helper method. It synchronizes the given application or module. This method finds the application or module in the configuration and delegates to the correct method. @param name name of an application or module @throws SynchronizationException if synchronization fails
it.eng.spagobi.kpi.ou.util.OrganizationalUnitSynchronizer.synchronize()
it.eng.spagobi.security.RoleSynchronizer.synchronize()
Syncronize the portal roles with SpagoBI roles importing roles missing in SpagoBI. if a role yet exist into SpagoBI table list, a tracing message is added and the list iteration goes on; if there is a new role, it is inserted into role database and another tracing message is added.
net.sf.logsaw.index.IIndexService.synchronize()
Synchronizes the log index for the given log resource. @param log the log resource to index @param monitor the progress monitor @throws CoreException if synchronization was interrupted by an error @return the number of log entries added
net.sf.logsaw.ui.ILogResourceManager.synchronize()
Triggers index synchronization for the given log resource.
This operation is being executed asynchronously. On finish callback will be called with the log resources that had changes as arguments. @param log the log resource to synchronize @param callback listener to be called upon completion @throws CoreException if an error occurred
net.tomp2p.synchronization.PeerSync.synchronize()
org.apache.felix.sigil.common.repository.IResolution.synchronize()
org.eclipse.ui.texteditor.IDocumentProviderExtension.synchronize()
Synchronizes the document provided for the given element with the given element. After that call getSynchronizationTimeStamp and getModificationTimeStamp return the same value. @param element the element @exception CoreException if the synchronization could not be performed
org.geoserver.security.AuthenticationKeyMapper.synchronize()
Assures that each user in the corresponding {@link GeoServerUserGroupService} hasan authentication key. returns the number of added authentication keys @throws IOException
org.ggf.drmaa.Session.synchronize()
Wait until all jobs specified by jobIds have finished execution. If jobIds contains JOB_IDS_SESSION_ALL, then this method waits for all jobs submitted during this DRMAA session up to the moment synchronize() is called. To avoid thread race conditions in multithreaded applications, the DRMAA implementation user should explicitly synchronize this call with any other job submission or control calls that may change the number of remote jobs.
To prevent blocking indefinitely in this call, the caller may use a timeout specifying how many seconds to block in this call. The value TIMEOUT_WAIT_FOREVER may be specified to wait indefinitely for a result. The value TIMEOUT_NO_WAIT may be specified to return immediately if no result is available. If the call exits before the timeout has elapsed, all the jobs have been waited on or there was an interrupt. If the invocation exits on timeout, an ExitTimeException is thrown. The caller should check system time before and after this call in order to be sure of how much time has passed.

The dispose parameter specifies how to treat the reaping of the remote jobs' internal data records, which includes a record of the jobs' consumption of system resources during their execution and other statistical information. If this parameter is set to true, the DRM will dispose of the jobs' data records at the end of the synchroniize() call. If set to false, the data records will be left for future access via the wait() method.
@param jobIds the ids of the jobs to synchronize @param timeout the maximum number of seconds to wait @param dispose specifies how to treat reaping information @throws DrmaaException May be one of the following:
- ExitTimeoutException -- the operation timed out before completing
- InvalidJobException -- the job identifier does not refer to an active job
- NoActiveSessionException -- the session has not yet been initialized or has already been exited
- DrmCommunicationException -- the DRMAA implementation was unable to contact the DRM
- AuthorizationException -- the executing user does not have sufficient permissions to execute the desired action
- IllegalArgumentException -- an argument is invalid
- InternalException -- an error has occured in the DRMAA implementation
@see #wait
org.nasutekds.quicksetup.util.FileManager.synchronize()
Recursively copies any files or directories appearing in source or a subdirectory of source to the corresponding directory under target. Files in under source are not copied to target if a file by the same name already exists in target. @param source source directory @param target target directory @throws ApplicationException if there is a problem copying files
org.nasutekds.server.admin.AdministrationDataSync.synchronize()
Check if information found in "cn=admin data" is coherent with cn=config. If and inconsistancy is detected, we log a warning message and update "cn=admin data"
org.springframework.richclient.selection.binding.support.ValueModel2EventListBridge.synchronize()
Synchronizes the EventList with the ValueModel. The values of the collection in the ValueModel are copied to the EventList. If the value in the ValueModel is null, the EventList will be emptied.

Examples of org.nasutekds.quicksetup.util.FileManager.synchronize()

        {
          return !Utils.isDescendant(f, oldConfigUpgradeDir);
        }
      };


      fm.synchronize(oldInstanceConfigDir, newInstanceConfigDir, filter);
    }
  }


  private void updateExtensionsDirectory()
          throws IOException,ApplicationException

View Full Code Here

Examples of org.nasutekds.server.admin.AdministrationDataSync.synchronize()

      // Determine whether or not we should synchronized admin data.
      if (! environmentConfig.disableAdminDataSynchronization())
      {
        AdministrationDataSync admDataSync = new AdministrationDataSync(
            rootConnection);
        admDataSync.synchronize();
      }


      // If a server.starting file exists, then remove it.
      File serverStartingFile =
                new File(configHandler.getInstanceRoot() + File.separator +

View Full Code Here

Examples of org.springframework.richclient.selection.binding.support.ValueModel2EventListBridge.synchronize()

            selectionDialog = new ListSelectionDialog("", null, eventList);
        }


        selectionDialog.setOnAboutToShow(new Block() {
            protected void handle(Object ignore) {
                itemRefresher.synchronize();
            }
        });


        selectionDialog.setOnSelectAction(new Closure() {
            public Object call(Object argument) {

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.