Package org.apache.camel.spi

Service Provider Interfaces used internally by the Camel runtime which are plugin strategies.

See:
          Description

Interface Summary
BrowsableEndpoint<T extends Exchange> An optional interface an Endpoint may choose to implement which allows it to expose a way of browsing the exchanges available.
ComponentResolver<E extends Exchange> Represents a resolver of components from a URI to be able to auto-load them using some discovery mechanism like DefaultComponentResolver
DataFormat Represents a data format used to marshal objects to and from streams such as Java Serialization or using JAXB2 to encode/decode objects using XML or using SOAP encoding.
ErrorHandlerWrappingStrategy The purpose of this interface is to allow an implementation to provide custom logic to wrap a processor with error handler
ExceptionHandler A Strategy pattern for handling exceptions; particularly in asynchronous processes such as consumers
ExchangeConverter This converter is capable of converting from an exchange to another type
HeaderFilterStrategy Interface to allow plug-able implementation to filter header to and from Camel message.
Injector A pluggable strategy for creating and possibly dependency injecting objects which could be implemented using straight forward reflection or using Spring or Guice to perform dependency injection.
InstrumentationAgent Camel JMX service agent
InterceptStrategy The purpose of this interface is to allow an implementation to wrap processors in a route with interceptors.
Language Represents a language to be used for Expression or Predicate instances
LanguageResolver A pluggable strategy for resolving different languages in a loosely coupled manner
LifecycleStrategy Strategy for lifecycle notifications.
NamespaceAware Represents an object which is aware of the namespaces in which its used such as XPath and XQuery type expressions so that the current namespace context can be injected
Policy<E> A strategy capable of applying interceptors to a processor
Provider<T> A provider of newly constructed objects
Registry Represents a service registry which may be implemented via a Spring ApplicationContext, via JNDI, a simple Map or the OSGI Service Registry
RouteContext The context used to activate new routing rules
Synchronization Provides a hook for custom Processor or Component instances to respond to completed or failed processing of an Exchange rather like Spring's TransactionSynchronization
TypeConverterAware An interface for an object which is interested in being injected with the root TypeConverter such as for implementing a fallback type converter
UnitOfWork An object representing the unit of work processing an Exchange which allows the use of Synchronization hooks.
 

Package org.apache.camel.spi Description

Service Provider Interfaces used internally by the Camel runtime which are plugin strategies.



Copyright © 2009 Apache Software Foundation. All Rights Reserved.