Table of Contents
The spring-event: component provides access to the Spring
ApplicationEvent objects. This allows you to publish
ApplicationEvent objects to a Spring ApplicationContext or to
consume them. You can then use
Enterprise Integration
Patterns to process them such as Message
Filter.
spring-event://default[?options]
Note, at the moment there are no options for this component. That can easily change in future releases, so please check back.
The Spring Event component supports 1 options which are listed below.
{% raw %}
| Name | Java Type | Description |
|---|---|---|
applicationContext |
| The Spring ApplicationContext |
{% endraw %}
The Spring Event component supports 5 endpoint options which are listed below:
{% raw %}
| Name | Group | Default | Java Type | Description |
|---|---|---|---|---|
name | common |
| Name of endpoint | |
bridgeErrorHandler | consumer |
|
| Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored. |
exceptionHandler | consumer (advanced) |
| To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored. | |
exchangePattern | consumer (advanced) |
| Sets the exchange pattern when the consumer creates an exchange. | |
synchronous | advanced |
|
| Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported). |
{% endraw %}