Examples of Execution

au.net.ocean.maven.plugin.annotation.Execution
br.eti.kinoshita.testlinkjavaapi.model.Execution
inoshita.eti.br @since 1.9.0-1
cat.quickdb.features20100702.model.Execution
@author Diego Sarmentero
com.gemstone.gemfire.cache.execute.Execution
com.mycila.testing.core.api.Execution
Represents a current execution of a method in a test @author Mathieu Carbou (mathieu.carbou@gmail.com)
edu.harvard.fas.zfeledy.fiximulator.core.Execution
mondrian.server.Execution
Execution context.
Loosely corresponds to a CellSet. A given statement may be executed several times over its lifetime, but at most one execution can be going on at a time.
@author jhyde
org.activiti.engine.runtime.Execution
Represent a 'path of execution' in a process instance. Note that a {@link ProcessInstance} also is an execution. @author Joram Barrez
org.apache.flink.runtime.executiongraph.Execution
A single execution of a vertex. While an {@link ExecutionVertex} can be executed multiple times (for recovery,or other re-computation), this class tracks the state of a single execution of that vertex and the resources. NOTE ABOUT THE DESIGN RATIONAL: In several points of the code, we need to deal with possible concurrent state changes and actions. For example, while the call to deploy a task (send it to the TaskManager) happens, the task gets cancelled. We could lock the entire portion of the code (decision to deploy, deploy, set state to running) such that it is guaranteed that any "cancel command" will only pick up after deployment is done and that the "cancel command" call will never overtake the deploying call. This blocks the threads big time, because the remote calls may take long. Depending of their locking behavior, it may even result in distributed deadlocks (unless carefully avoided). We therefore use atomic state updates and occasional double-checking to ensure that the state after a completed call is as expected, and trigger correcting actions if it is not. Many actions are also idempotent (like canceling).
org.apache.maven.plugin.lifecycle.Execution
A set of goals to execute. @version $Revision$ $Date$
org.apache.stanbol.enhancer.servicesapi.helper.execution.Execution
The Execution of an EnhancementEngine as defined by the {@link #getExecutionNode()} @author Rupert Westenthaler
org.archfirst.bfexch.domain.trading.order.Execution
Execution @author Naresh Bhatia
org.camunda.bpm.engine.runtime.Execution
Represent a 'path of execution' in a process instance. Note that a {@link ProcessInstance} also is an execution. @author Joram Barrez
org.jboss.forge.addon.maven.plugins.Execution
Represents an element in the pom.xml @author George Gastaldi
org.jboss.forge.shell.command.Execution
@author Lincoln Baxter, III @author Koen Aers
org.jbpm.api.Execution
a runtime path of execution.
State of an execution

The state of an execution is either active or locked. An active execution is either executing or waiting for an external trigger. If an execution is not in {@link #STATE_ACTIVE_ROOT}or {@link #STATE_ACTIVE_CONCURRENT} then it is locked. A locked execution is read only.

When a new execution is created, it is in {@link #STATE_ACTIVE_ROOT}. {@link #STATE_ACTIVE_ROOT Some STATE_* constants} are provided that represent the most commonly used locked states. But the state '...' in the picture indicates that any string can be provided as the state in the lock method.

If an execution is locked, methods that change the execution will throw a {@link JbpmException} and the message will reference the actual locking state.{@link OpenExecution#setVariable(String,Object) updating variables}, {@link OpenExecution#setPriority(int) updating priority} are not considered to change an execution.

Make sure that comparisons between {@link #getState()} and the {@link #STATE_ACTIVE_ROOT STATE_* constants} are done with .equals and not with '==' because if executions are loaded from persistent storage, a new string is created instead of the constants.

Comments
@author Tom Baeyens
org.jbpm.pvm.Execution
a runtime path of execution.
State of an execution

The state of an execution is either active or locked. An active execution is either executing or waiting for an external trigger. If an execution is not in {@link #STATE_ACTIVE}, then it is locked. A locked execution is read only.

When a new execution is created, it is in {@link #STATE_ACTIVE}. To change the state to a locked state, use {@link #lock(String)}. {@link #STATE_ACTIVE Some STATE_* constants} are provided that represent the most commonly used locked states. But the state '...' in the picture indicates that any string can be provided as the state in the lock method.

If an execution is locked, methods that change the execution will throw a {@link PvmException} and the message will reference the actual locking state.{@link #fire(String,ObservableElement) Firing events}, {@link #setVariable(String,Object) updating variables}, {@link #setPriority(int) updating priority} and {@link #addComment(String) adding comments} are not considered to change an execution. Also {@link #createExecution(String) creation} and {@link #removeExecution(Execution) removal} of child executions are unchecked, which means that those methods can be invoked by external API clients and node behaviour methods, even while the execution is in a locked state.

Make sure that comparisons between {@link #getState()} and the {@link #STATE_ACTIVE STATE_* constants} are done with .equals and not with '==' because if executions are loaded from persistent storage, a new string is created instead of the constants.

Comments
@author Tom Baeyens
org.seleniumhq.selenium.fluent.internal.Execution
org.soybeanMilk.core.Execution
执行语境信息。
如果你为框架添加了执行拦截器（参考 {@linkplain Interceptor 执行拦截器信息}类），或许想要在你的拦截器中获取这些执行语境信息。 @author earthangry@gmail.com @date 2010-11-28
org.teiid.translator.Execution
An execution represents the state and lifecycle for a particular command execution. The methods provided on this interface define standard lifecycle methods. When execution completes, the {@link #close()} will be called. If execution must be aborted, due to user or administrator action, the {@link #cancel()} will be called.
org.xsocket.Execution
org.zkoss.zk.ui.Execution
An execution of a client request (e.g., ServletRequest). When a request sent from a client, the server constructs a {@link Execution}object to hold execution relevant info, and then serves the request thru this execution.
A client request, e.g., HttpServletRequest, might consist of multiple ZK request ( {@link org.zkoss.zk.au.AuRequest}). However, these ZK requests must target the same desktop of pages ( {@link Page}).
Because a request might come from HTTP or other protocol, Execution also serves as an isolation layer. @author tomyeh @see Page
quickdb.features20100702.model.Execution
@author Diego Sarmentero
quickfix.banzai.Execution
ratpack.exec.Execution
A logical stream of execution, which is potentially serialized over many threads.
Ratpack is non blocking. This requires that IO and other blocking operations are performed asynchronously. In completely synchronous execution, the thread and the call stack serve as the representation of a stream of execution, with the execution being bound to a single thread exclusively for its entire duration. The {@code Execution} concept in Ratpack brings some of the characteristics of the traditional single-thread exclusive modelto the asynchronous, non-exclusive, environment.
A well understood example of a logical stream of execution in the web application environment is the handling of a request. This can be thought of as a single logical operation; the request comes in and processing happens until the response is sent back. Many web application frameworks exclusively assign a thread to such a stream of execution, from a large thread pool. If a blocking operation is performed during the execution, the thread sits waiting until it can continue (e.g. the IO completes, or the contended resource becomes available). Thereby the segments of the execution are serialized and the call stack provides execution context. Ratpack supports the non-blocking model, where threads do not wait. Instead of threads waiting for IO or some future event, they are returned to the “pool” to be used by other executions (and therefore the pool can be smaller). When the IO completes or the contended resource becomes available, execution continues with a new call stack and possibly on a different thread.
The execution object underpins an entire logical operation, even when that operation may be performed by multiple threads.
Importantly, it also serializes execution segments by way of the {@link ratpack.exec.ExecControl#promise(ratpack.func.Action)} method.These methods are fundamentally asynchronous in that they facilitate performing operations where the result will arrive later without waiting for the result, but are synchronous in the operations the perform are serialized and not executed concurrently or in parallel. Crucially, this means that state that is local to an execution does not need to be thread safe.
Executions and request handling

The execution object actually underpins the {@link ratpack.handling.Context} objects that are used when handling requests.It is rarely used directly when request handling, except when concurrency or parallelism is required to process data via the {@link ratpack.handling.Context#exec()} method.Moreover, it provides its own error handling and completion mechanisms.

Examples of org.zkoss.zk.ui.Execution

   * 
   * @param component
   *            target component
   */
  public static void setSelfContextComponent(Component component) {
    final Execution exec = Executions.getCurrent();
    final VariableResolver vresolver = exec.getVariableResolver();
    ((ExecutionResolver) vresolver).setSelf(component);
  }

View Full Code Here

Examples of quickdb.features20100702.model.Execution

        System.out.println("testOptimisticLock");
        this.testOptimisticLock();
    }


    public void testBeforeAfterSameClass(){
        Execution e = new Execution();
        e.setDescription("description");
        e.setValue(5);


        System.out.println(admin.save(e));


        System.out.println(22 == e.getValue());


        admin.obtain(e).If("description").equal("description").find();
        System.out.println(999 == e.getValue());
    }

View Full Code Here

Examples of quickfix.banzai.Execution

        super(executionTableModel);
    }


    public Component prepareRenderer(TableCellRenderer renderer,
                                     int row, int column) {
        Execution execution = (Execution)((ExecutionTableModel)dataModel)
                              .getExecution(row);


        DefaultTableCellRenderer r = (DefaultTableCellRenderer)renderer;
        r.setForeground(Color.black);

View Full Code Here

Examples of ratpack.exec.Execution

  }


  @Override
  @SuppressWarnings("unchecked")
  public T get() {
    Execution execution = getExecution();


    HystrixCommandCache commandCache = execution.maybeGet(HystrixCommandCache.class)
      .orElseGet(() -> {
        HystrixCommandCache cache = new HystrixCommandCache();
        execution.add(cache);
        return cache;
      });


    Object command = commandCache.get(this);
    if (command == null) {

View Full Code Here

0 1 2 3 4 5 6 7

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.

Examples of Execution

State of an execution

Comments

State of an execution

Comments

Executions and request handling

Examples of org.zkoss.zk.ui.Execution

Examples of quickdb.features20100702.model.Execution

Examples of quickfix.banzai.Execution

Examples of ratpack.exec.Execution