Passing data between pipesAdded by IBM on May 5, 2011 | Version 1 (Original)
|Pipes work together in a pipeline. Most pipes must receive information from the pipeline as well as pass on new information to the pipeline for use by other pipes using the data bucket. This is done using pipe parameters. Tags: data: passing data in and out of pipes, getter method, setter method, methods, JavaBean, pipes, bundle.properties, evaluateGet method, evaluateSet method, referencing an object, objects, Object parameter, parameters, Map parameter, Pipe, interfaces, extending PipeImpl class, FSP, 220.127.116.11, developing, 18.104.22.168
Pipes work together in a pipeline. Most pipes must receive information from the pipeline as well as pass on new information to the pipeline for use by other pipes using the data bucket. This is done using pipe parameters.
Each pipe defines its own parameters using getter and setter methods that conform to the JavaBeans™ naming conventions. To pass data into or out of a pipe, you must create JavaBean getter and setter methods. These methods get or set private variables that are used inside the performWork method. These method names must match names of configuration entries in *.properties configuration files, or the pipe will ignore them. The data provided by the getter and setter methods do not contain actual values; rather, they provide a reference to the object. To convert the reference to an actual object, you must use the evaluateGet and evaluateSet methods, which will pass the actual data bucket values to the performWork method using the databucket
Additional parameter information can be set on the WorkRequest prior to running the Action branch. For detailed information, see the Forms Services Platform API documentation.
Using pipeline parameters
You use pipeline parameters to pass data between pipelines.
Passing values in and out of pipes
Pipes execute sequentially and often require data from previous pipes to perform their tasks. Therefore, you need to be able to pass information in and out of pipes. This is done by defining the type of information you want to pass in or out and where the information is coming from or going to.
Parent topic: Forms Services Platform technical overview