Class ForPipe

All Implemented Interfaces:
HasTransactionAttribute, IConfigurable, IConfigurationAware, IForwardTarget, INamedObject, IPipe, IScopeProvider, IWithParameters, EventThrowing, HasStatistics, org.springframework.beans.factory.Aware, org.springframework.context.ApplicationContextAware

@Forward(name="stop",description="exit for loop") @Forward(name="continue",description="continue in for loop") @ElementType(ITERATOR) public class ForPipe extends AbstractPipe
ForPipe is a wrapper to use another pipe a fixed number of times. This can be accomplished by something like:

 		<ForPipe name="forPipe" startAt="0" stopAt="10">
 		 	<Forward name="stop" path="EXIT" />
 		 	<Forward name="continue" path="echoPipe"/>
 		</ForPipe>

 		<EchoPipe name="echoPipe" getInputFromSessionKey="forPipe.iteration">
 		 	<Forward name="success" path="forPipe"/>
 		</EchoPipe>
 

This should call the echoPipe for i=0 until i=10.

Author:
evandongen
  • Constructor Details

    • ForPipe

      public ForPipe()
  • Method Details

    • configure

      public void configure() throws ConfigurationException
      Description copied from class: AbstractPipe
      configure() is called after the Pipeline is registered at the Adapter. Purpose of this method is to reduce creating connections to databases etc. in the doPipe() method. As much as possible class-instantiating should take place in the configure() method, to improve performance.
      Specified by:
      configure in interface IConfigurable
      Specified by:
      configure in interface IPipe
      Overrides:
      configure in class AbstractPipe
      Throws:
      ConfigurationException
    • doPipe

      public PipeRunResult doPipe(Message message, PipeLineSession session) throws PipeRunException
      Description copied from interface: IPipe
      This is where the action takes place. Pipes may only throw a PipeRunException, to be handled by the caller of this object. Implementations must either consume the message, or pass it on to the next Pipe in the PipeRunResult. If the result of the Pipe does not depend on the input, like for the FixedResultPipe, the Pipe can schedule the input to be closed at session exit, by calling Message.closeOnCloseOf(PipeLineSession, String) This allows the previous Pipe to release any resources (e.g. connections) that it might have kept open until the message was consumed. Doing so avoids connections leaking from pools, while it enables efficient streaming processing of data while it is being read from a stream.
      Throws:
      PipeRunException
    • setStartAt

      public void setStartAt(int startAt)
      Starts counting at this value.
      Default value
      0
    • setStopAt

      public void setStopAt(Integer stopAt)
      Break from the loop when incrementSessionKey equals this value
    • getStartAt

      public int getStartAt()
    • getStopAt

      public Integer getStopAt()