Class PutParametersInSession

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

@Deprecated(forRemoval=true, since="7.7.0") @ConfigurationWarning("Please replace with PutInSessionPipe") public class PutParametersInSession extends FixedForwardPipe
Deprecated, for removal: This API element is subject to removal in a future version.
Stores parameter values in the PipeLineSession.
Author:
Peter Leeuwenburgh
Parameters
the result of each parameter defined will be we stored in the PipeLineSession, under the key specified by the parameter name
  • Constructor Details

    • PutParametersInSession

      public PutParametersInSession()
      Deprecated, for removal: This API element is subject to removal in a future version.
  • Method Details

    • doPipe

      public PipeRunResult doPipe(Message message, PipeLineSession session) throws PipeRunException
      Deprecated, for removal: This API element is subject to removal in a future version.
      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