[[spring-event-component]]
= Spring Event Component
:page-source: components/camel-spring/src/main/docs/spring-event-component.adoc

*Available as of Camel version 1.4*


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
xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] to process them such as xref:latest@manual::filter-eip.adoc[Message
Filter].

== URI format

[source,java]
--------------------------------
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.

== Spring Event Options



// component options: START
The Spring Event component has no options.
// component options: END




// endpoint options: START
The Spring Event endpoint is configured using URI syntax:

----
spring-event:name
----

with the following path and query parameters:

=== Path Parameters (1 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *name* | Name of endpoint |  | String
|===


=== Query Parameters (4 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *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 or ERROR level and ignored. | false | boolean
| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer creates an exchange. |  | ExchangePattern
| *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
|===
// endpoint options: END
// spring-boot-auto-configure options: START
== Spring Boot Auto-Configuration

When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:

[source,xml]
----
<dependency>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-spring-starter</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel core version -->
</dependency>
----


The component supports 4 options, which are listed below.



[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *camel.component.spring-event.enabled* | Enable spring-event component | true | Boolean
| *camel.component.spring-event.resolve-property-placeholders* | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | Boolean
| *camel.language.spel.enabled* | Enable spel language | true | Boolean
| *camel.language.spel.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
|===
// spring-boot-auto-configure options: END
