Examples of Trigger

• DisplayProject.binding.value.Trigger
  A ValueModel implementation that is intended to be used as trigger channel for instances of BufferedValueModel. API users shall trigger commit and flush events using #triggerCommit and #triggerFlush.

  This Trigger class works around an inconvenient situation when using a general ValueHolder as trigger channel of a BufferedValueModel. BufferedValueHolder performs commit and flush events only if the trigger channel value reports a change. And a ValueHolder doesn't report a change if #setValue tries to set the current value. For example if you set Boolean.TRUE twice, the latter doesn't fire a property change event. The methods #triggerCommit and #triggerFlush check for the current state and guarantee that the appropriate PropertyChangeEvent is fired. On the other hand, the implementation minimizes the number of events necessary to commit or flush buffered values.

  Constraints: The value is of type Boolean.

  The following example delays the commit of a buffered value:

   ValueModel subject = new ValueHolder(); Trigger trigger = new Trigger(); BufferedValueModel buffer = new BufferedValueModel(subject, trigger); buffer.setValue("value"); ... trigger.triggerCommit(); 

  @author Karsten Lentzsch @version $Revision: 1.5 $ @see BufferedValueModel Copyright (c) 2002-2005 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• at.bestsolution.efxclipse.runtime.bindings.Trigger
• at.jku.sii.sqlitereader.model.Trigger
• ch.njol.skript.lang.Trigger
  @author Peter Güttinger
• com.caucho.config.types.Trigger
  Trigger for schedules and cron jobs
• com.epicsagaonline.bukkit.ChallengeMaps.objects.Trigger
• com.jgoodies.binding.value.Trigger
• com.jme3.input.controls.Trigger
  A trigger represents a physical input, such as a keyboard key, a mouse button, or joystick axis.
• com.netflix.astyanax.recipes.queue.triggers.Trigger
  Base interface for all triggers. Triggers specify the scheduling for a task in the scheduler. Different implementation of trigger can specify different triggering semantics. @author elandau
• com.quartz.monitor.object.Trigger
• com.sleepycat.je.trigger.Trigger
  DatabasetTrigger defines the trigger methods associated with a database. They provide a mechanism to track the database definition operations used to manage the lifecycle of the database itself, as well as the record operations used to modify the contents of the database.

  The following table captures the relationship between the database granularity operations and their associated trigger methods.

  Database Operation	Trigger Method
  {@link Environment#openDatabase Environment.openDatabase} resulting inthe creation of a new primary database. Or the first open of a database for write operations.	{@link #open open}
  {@link Database#close Database.close} the close of a database that wasopened for write operations.	{@link #close close}
  {@link Environment#removeDatabase Environment.removeDatabase}	{@link #remove remove}
  {@link Environment#truncateDatabase Environment.truncateDatabase}	{@link #truncate truncate}
  {@link Environment#renameDatabase Environment.renameDatabase}	{@link #rename truncate}

  The trigger methods {@link #put put} and {@link #delete delete} are used totrack all record operations on the database.

  A trigger method takes a transaction as its first argument. If the environment is not transactional, the argument is null. In all other cases, it's a valid transaction ( {@link Transaction#isValid() Transaction.isValid}is true) and the trigger can use this transaction to make it's own set of accompanying changes.

  If the invocation of a trigger results in a runtime exception, the transaction (if one was associated with the method) is invalidated and any subsequent triggers associated with the operation are skipped. It's the caller's responsibility to handle the exception and abort the invalidated transaction. If the exception is thrown during the replay of a transaction on a replica in an HA application, the environment is invalidated and a new environment handle must be created.

  A Trigger is associated with a database via {@link DatabaseConfig#setTriggers DatabaseConfig.setTriggers}.

  Note that all subtypes of Trigger must be serializable, because they are stored persistently in the environment.
• com.squareup.pagerduty.incidents.Trigger
• eu.planets_project.pp.plato.model.Trigger
  Represents a certain trigger. Only triggers that are selected by the user are stored in the preservation plan. The list of existing triggers is defined in {@link #getAllDefinedTriggers()} @author Hannes Kulovits
• eu.scape_project.planning.model.Trigger
  Represents a certain trigger. Only triggers that are selected by the user are stored in the preservation plan. The list of existing triggers is defined in {@link #getAllDefinedTriggers()} @author Hannes Kulovits
• eu.scape_project.watch.domain.Trigger
• hudson.triggers.Trigger
  Triggers a {@link Build}.

  To register a custom {@link Trigger} from a plugin,put {@link Extension} on your {@link TriggerDescriptor} class. @author Kohsuke Kawaguchi

• it.freedomotic.reactions.Trigger
  @author enrico
• javax.enterprise.concurrent.Trigger
  Triggers allow application developers to plug in rules for when and how often a task should run. The trigger can be as simple as a single, absolute date-time or can include Java™ EE business calendar logic. A Trigger implementation is created by the application developer (or may be supplied to the application externally) and is registered with a task when it is submitted to a {@link ManagedScheduledExecutorService} using any of the schedule methods. Each method will run with unspecified context unless {@link ManagedTask#CONTEXTUAL_CALLBACK_HINT} is specified to control whetheror not these callback methods run under the same context in which the task runs.

  Each Trigger instance will be invoked within the same process in which it was registered.

  Trigger should be Serializable if it is to be used on a distributed {@code ManagedScheduledExecutorService}.

  Example:

   / * A trigger that only returns a single date. */ public class SingleDateTrigger implements Trigger { private Date fireTime; public TriggerSingleDate(Date newDate) { fireTime = newDate; } public Date getNextRunTime( LastExecution lastExecutionInfo, Date taskScheduledTime) { if(taskScheduledTime.after(fireTime)) { return null; } return fireTime; } public boolean skipRun(LastExecution lastExecutionInfo, Date scheduledRunTime) { return scheduledRunTime.after(fireTime); } } / * A fixed-rate trigger that will skip any runs if * the latencyAllowance threshold is exceeded (the task * ran too late). */ public class TriggerFixedRateLatencySensitive implements Trigger { private Date startTime; private long delta; private long latencyAllowance; public TriggerFixedRateLatencySensitive(Date startTime, long delta, long latencyAllowance) { this.startTime = startTime; this.delta = delta; this.latencyAllowance = latencyAllowance; } public Date getNextRunTime(LastExecution lastExecutionInfo,  Date taskScheduledTime) { if(lastExecutionInfo==null) { return startTime; } return new Date(lastExecutionInfo.getScheduledStart().getTime() + delta); } public boolean skipRun(LastExecution lastExecutionInfo, Date scheduledRunTime) { return System.currentTimeMillis() - scheduledRunTime.getTime() > latencyAllowance; } } 

  @since 1.0

• net.fortuna.ical4j.model.property.Trigger
• net.helipilot50.stocktrade.displayproject.binding.value.Trigger
  A ValueModel implementation that is intended to be used as trigger channel for instances of BufferedValueModel. API users shall trigger commit and flush events using #triggerCommit and #triggerFlush.

  This Trigger class works around an inconvenient situation when using a general ValueHolder as trigger channel of a BufferedValueModel. BufferedValueHolder performs commit and flush events only if the trigger channel value reports a change. And a ValueHolder doesn't report a change if #setValue tries to set the current value. For example if you set Boolean.TRUE twice, the latter doesn't fire a property change event. The methods #triggerCommit and #triggerFlush check for the current state and guarantee that the appropriate PropertyChangeEvent is fired. On the other hand, the implementation minimizes the number of events necessary to commit or flush buffered values.

  Constraints: The value is of type Boolean.

  The following example delays the commit of a buffered value:

   ValueModel subject = new ValueHolder(); Trigger trigger = new Trigger(); BufferedValueModel buffer = new BufferedValueModel(subject, trigger); buffer.setValue("value"); ... trigger.triggerCommit(); 

  @author Karsten Lentzsch @version $Revision: 1.5 $ @see BufferedValueModel Copyright (c) 2002-2005 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• nexj.core.meta.workflow.Trigger
  Step for triggering script execution with events.
• org.apache.ivy.plugins.trigger.Trigger
• org.apache.openejb.quartz.Trigger
• org.cfeclipse.cfml.dictionary.Trigger
  Trigger - represents the attribute conditions required to trigger (allow) an attribute to be available. For example, on the tag the parameter 'source' is available when the 'append' attribute is set to either: copy,move or rename. When that occurs it is not only available, but required as well. @author Oliver Tupman
• org.cspoker.common.api.shared.Trigger
• org.drools.core.time.Trigger
  A trigger interface for scheduling jobs
• org.drools.time.Trigger
  A trigger interface for scheduling jobs
• org.drools.workflow.core.node.Trigger
• org.eclipse.jface.bindings.Trigger

  The abstract class for any object that can be used as a trigger for a binding. This ensures that trigger conform to certain minimum requirements. Namely, triggers need to be hashable.

  @since 3.1
• org.h2.api.Trigger
  A class that implements this interface can be used as a trigger.
• org.jboss.mbui.model.structure.Trigger
  The trigger element is used to specify a command from the user perspective. This might be a function call or a navigation trigger.

  It consists of an interaction unit id, but also requires a specific trigger type declaration that specifies the output of this unit. @author Heiko Braun @date 1/16/13

• org.jboss.seam.cron.api.scheduling.Trigger

  The payload of all scheduled events, be they arbitrarily scheduled or one of the built-in @Every() schedules. Note that the presence of this superclass implies that the following observation is possible: public void doSomething(@Observes @Every Trigger e)

  Such an observation is valid, and will respond to every single scheduled event fired (including the built in events).

  @author Peter Royle
• org.jbpm.workflow.core.node.Trigger
• org.jwatch.domain.quartz.Trigger
  @author Roy RussoDate: Apr 20, 2011 9:37:08 AM
• org.mitre.sim.Trigger
  Abstract superclass of all developer-defined triggers. Entities can wait until some condition becomes true in the simulation environment by defining a subclass of Trigger that embodies the desired condition, and invoking {@link org.mitre.sim.Entity#waitForActionOrTrigger(Trigger) waitForActionOrTrigger}. See the summary section, "Triggers."
  

  
  Copyright © 2003-2004 The MITRE Corporation

• org.openntf.domino.xots.annotations.Trigger
• org.quartz.Trigger

  The base abstract class to be extended by all Triggers.

  Triggers s have a name and group associated with them, which should uniquely identify them within a single {@link Scheduler}.

  Triggers are the 'mechanism' by which Job s are scheduled. Many Trigger s can point to the same Job, but a single Trigger can only point to one Job.

  Triggers can 'send' parameters/data to Jobs by placing contents into the JobDataMap on the Trigger.

  @see SimpleTrigger @see CronTrigger @see NthIncludedDayTrigger @see TriggerUtils @see JobDataMap @see JobExecutionContext @author James House @author Sharada Jambula
• org.restsql.core.Trigger
  Provides a mechanism for executing non-trivial domain validation or business logic on all CRUD operations. Throwing {@link InvalidRequestException} from a beforeXxx() will stop the transaction and return HTTP 400 BadRequest to the client. Throwing {@link SqlResourceException} from a beforeXxx() orafterXxx() will return HTTP 500 Internal Server Error to the client. @author Mark Sawers @see AbstractTrigger
• org.sbml.jsbml.Trigger
  Represents the trigger XML element of a SBML file. @author Andreas Dräger @since 0.8 @version $Rev: 1524 $
• org.sbml.libsbml.Trigger
• org.springframework.scheduling.Trigger
  Common interface for trigger objects that determine the next execution time of a task that they get associated with. @author Juergen Hoeller @since 3.0 @see TaskScheduler#schedule(Runnable,Trigger) @see org.springframework.scheduling.support.CronTrigger
• org.uispec4j.Trigger
  Interface for window interception triggers - UI interactions which display a window.

  Ready-to-use triggers are made available by several components such as Buttons or Menus. @see Button#triggerClick @see MenuItem#triggerClick @see WindowInterceptor

• org.useware.kernel.model.structure.Trigger
  The trigger element is used to specify a command from the user perspective. This might be a function call or a navigation trigger.

  It consists of an interaction unit id, but also requires a specific trigger type declaration that specifies the output of this unit. @author Heiko Braun @date 1/16/13

Examples of org.sbml.libsbml.Trigger

Examples of org.springframework.scheduling.Trigger

Examples of org.uispec4j.Trigger

Examples of org.useware.kernel.model.structure.Trigger