Each master maintains its own object store, which is simply a map relating keys to objects. Once stored, the objects remain until explicitly deleted. This provides a way to pass information between exits and even between workflows. Using the object store, you can implement stateful workflows. If your input provides a correlation ID (for example, JMS or MQ) this often makes a good key for maintaining state information.
Name |
Description |
---|---|
getObject |
Retrieves an object stored under a key. |
setObject |
Adds an arbitrary object to the object store under a designated key. Setting the null object removes the key from the object store. |
iWay Software |