Examples of StatusManager

ch.qos.logback.core.status.StatusManager
Internal error messages (statii) are managed by instances of this interface. @author Ceki Gulcu
com.alibaba.dubbo.registry.common.StatusManager
StatusManager @author william.liangf
com.cloudera.flume.master.StatusManager
This manages the last seen and heartbeat data on the master flume configuration node. There should be no references to Thrift here.
com.google.collide.client.status.StatusManager
The Status Manager is responsible for maintaining all status state. It coordinates priorities between different types of messages and allows the status view to be stateless. There can be many outstanding messages at any given time, but only one message is active. When a message becomes active, the {@link StatusHandler}is notified of this change. A fatal message is unrecoverable and cannot be dismissed or canceled once fired.
org.apache.ivy.core.module.status.StatusManager
Note: update methods (such as addStatus) should only be called BEFORE any call to accessor methods @author x.hanin
org.eclipse.ui.statushandlers.StatusManager
StatusManager is the entry point for all statuses to be reported in the user interface.

Handlers shoudn't be used directly but through the StatusManager singleton which keeps the status handling policy and chooses handlers. StatusManager.getManager().handle(IStatus) and handle(IStatus status, int style) are the methods are the primary access points to the StatusManager.

Acceptable styles (can be combined with logical OR)
- NONE - a style indicating that the status should not be acted on. This is used by objects such as log listeners that do not want to report a status twice
- LOG - a style indicating that the status should be logged only
- SHOW - a style indicating that handlers should show a problem to an user without blocking the calling method while awaiting user response. This is generally done using a non modal {@link Dialog}
- BLOCK - a style indicating that the handling should block the calling method until the user has responded. This is generally done using a modal window such as a {@link Dialog}
Handlers are intended to be accessed via the status manager. The StatusManager chooses which handler should be used for a particular error. There are two ways for adding handlers to the handling flow. First using extension point org.eclipse.ui.statusHandlers, second by the workbench advisor and its method {@link WorkbenchAdvisor#getWorkbenchErrorHandler()}. If a handler is associated with a product, it is used instead of this defined in advisor.
@since 3.3 @see AbstractStatusHandler
voldemort.server.StatusManager

Examples of org.apache.ivy.core.module.status.StatusManager

                if ("true".equals(_ivy.substitute((String)attributes.get("usedefaults")))) {
                    _ivy.configureDefaultVersionMatcher();
                }
            } else if ("statuses".equals(qName)) {
                _currentConfiguratorTag = qName;
                StatusManager m = new StatusManager();
                String defaultStatus = _ivy.substitute((String)attributes.get("default"));
                if (defaultStatus != null) {
                    m.setDefaultStatus(defaultStatus);
                }
                _ivy.setStatusManager(m);
                _configurator.setRoot(m);
            } else if (_configuratorTags.contains(qName)) {
                _currentConfiguratorTag = qName;

View Full Code Here

Examples of org.eclipse.ui.statushandlers.StatusManager

    public static void log(IStatus status) {
  int style = StatusManager.LOG;


  if (status.getSeverity() == IStatus.ERROR) {
      style = StatusManager.LOG | StatusManager.SHOW | StatusManager.BLOCK;
      StatusManager stMan = StatusManager.getManager();
      stMan.handle(status, style);
  } else {
      Activator.getDefault().getLog().log(status);
  }


    }

View Full Code Here

Examples of voldemort.server.StatusManager

        this.endpoint = new InetSocketAddress(port);


        this.selectorManagers = new NioSelectorManager[selectors];
        this.selectorManagerThreadPool = Executors.newFixedThreadPool(selectorManagers.length,
                                                                      new DaemonThreadFactory("voldemort-niosocket-server"));
        this.statusManager = new StatusManager((ThreadPoolExecutor) this.selectorManagerThreadPool);
        this.acceptorThread = new Thread(new Acceptor(), "NioSocketService.Acceptor");
    }

View Full Code Here

Examples of voldemort.server.StatusManager

                                                 0,
                                                 TimeUnit.MILLISECONDS,
                                                 new SynchronousQueue<Runnable>(),
                                                 threadFactory,
                                                 rejectedExecutionHandler);
        this.statusManager = new StatusManager(this.threadPool);
        this.sessionIdSequence = new AtomicLong(0);
        this.activeSessions = new ConcurrentHashMap<Long, SocketServerSession>();
        this.serverName = serverName;
        this.logger = Logger.getLogger(SocketServer.class.getName() + "[" + serverName + "]");
    }

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.