Alternative event-handling solutions should be used
Please consider using one the following alternatives: No alternative components suggested.
A Processor that supports sending and receiving data from application defined in Spring Application Context via predefined in/out MessageChannels.
Spring, Message, Get, Put, Integration
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Application Context config path | Application Context config path | The path to the Spring Application Context configuration file relative to the classpath | ||
| Application Context class path | Application Context class path | Path to the directory with resources (i.e., JARs, configuration files etc.) required to be on the classpath of the ApplicationContext. This property requires exactly one directory to be provided.. | ||
| Send Timeout | Send Timeout | Timeout for sending data to Spring Application Context. Defaults to 0. | ||
| Receive Timeout | Receive Timeout | Timeout for receiving date from Spring context. Defaults to 0. |
| Name | Description |
|---|---|
| success | All FlowFiles that are successfully received from Spring Application Context are routed to this relationship |
| failure | All FlowFiles that cannot be sent to Spring Application Context are routed to this relationship |