- Apache Camel Developer's Cookbook
- Table of Contents
- Apache Camel Developer's Cookbook
- Credits
- About the Authors
- Acknowledgments
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Structuring Routes
- Introduction
- Using Camel in a Java application
- Embedding Camel in a Spring application
- Using Camel components
- Reusing routing logic by connecting routes
- Asynchronously connecting routes
- Spanning Camel contexts within a single Java process
- Using external properties in Camel routes
- Reusing endpoints
- Reusing routing logic through template routes
- Controlling route startup and shutdown
- 2. Message Routing
- Introduction
- Content Based Routing
- Filtering out unwanted messages
- Wire Tap – sending a copy of the message elsewhere
- Multicast – routing the same message to many endpoints
- Recipient List – routing a message to a list of endpoints
- Throttler – restricting the number of messages flowing to an endpoint
- Request-response route sending a one-way message
- One-way route waiting on a request-response endpoint
- Dynamic Routing – making routing decisions at runtime
- Load balancing across a number of endpoints
- Routing Slip – routing a message to a fixed list of endpoints
- 3. Routing to Your Code
- 4. Transformation
- Introduction
- Transforming using a Simple Expression
- Transforming inline with XQuery
- Transforming with XSLT
- Transforming from Java to XML with JAXB
- Transforming from Java to JSON
- Transforming from XML to JSON
- Parsing comma-separated values (CSV)
- Enriching your content with some help from other endpoints
- Normalizing messages into a common XML format
- 5. Splitting and Aggregating
- Introduction
- Splitting a message into fragments
- Splitting XML messages
- Processing split messages in parallel
- Aggregating related messages
- Aggregating with timeouts
- Aggregating with intervals
- Processing aggregated messages in parallel
- Splitting a message, and processing and gathering responses
- Splitting messages and re-aggregating them using different criteria
- 6. Parallel Processing
- 7. Error Handling and Compensation
- Introduction
- Logging errors
- Dead Letter Channel – handling errors later
- Retrying an operation
- Conditional retry
- Customizing each redelivery attempt
- Catching exceptions
- Marking exceptions as handled
- Fine-grained error handling using doTry…doCatch
- Defining completion actions
- Defining completion actions dynamically
- 8. Transactions and Idempotency
- Introduction
- Preventing duplicate invocation of routing logic
- Transactional file consumption
- Using transactions with a database
- Limiting the scope of a transaction
- Rolling back a transaction
- Using transactions with messaging
- Idempotency inside transactions
- Setting up XA transactions over multiple transactional resources
- 9. Testing
- Introduction
- Testing routes defined in Java
- Using mock endpoints to verify routing logic
- Replying from mock endpoints
- Testing routes defined in Spring
- Testing routes defined in OSGi Blueprint
- Auto-mocking of endpoints
- Validating route behavior under heavy load
- Unit testing processors and Bean Bindings
- Testing routes with fixed endpoints using AOP
- Testing routes with fixed endpoints using conditional events
- 10. Monitoring and Debugging
- Introduction
- Logging meaningful steps within your route
- Debugging using logging
- Throughput logging
- Enabling step-by-step tracing in code
- Disabling JMX
- Configuring JMX
- Naming your routes to make it easier to monitor
- Adding JMX attributes and operations
- Monitoring other systems using the Camel JMX Component
- Setting breakpoints in your routes
- 11. Security
- 12. Web Services
- Index
When an endpoint is going to be used multiple times in a Camel context it is preferable to define it at a single place so that it is used consistently. This recipe will show you a way to do that.
Define your desired routing logic as described in either the Using Camel in a Java application recipe, or the Embedding Camel in a Spring application recipe.
In the XML DSL, define an <endpoint/> element with an id attribute and an uri attribute setting that is set to the URI value you wish to share:
<camelContext xmlns="..."> <endpoint id="restfulOrdersService" uri="jetty:http://localhost:8080/orders"/> <route> <from ref="restfulOrdersService"/> <!-- ... --> </route> </camelContext>
If using the Java DSL, simply define the URI as a String within RouteBuilder configure() method:
String restfulOrdersService =
"jetty:http://localhost:8080/orders";
from(restfulOrdersService) //...-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.