Chapter 3. Using Sender Endpoints
Abstract
Sender endpoints write messages to the file system.
Important
The Java Business Integration components of Red Hat JBoss Fuse are considered deprecated. You should consider migrating any JBI applications to OSGi.
3.1. Introduction to sender endpoints
Overview
The function of a sender endpoint is to write data, in the form of files, to a location on a file system. You can control the location of the files written to the file system and have some control over the name of the generated files. You can also control if data is appended to existing files or if new copies of a file are created.
By default, sender endpoints write XML data to the file system. You can change this behavior by configuring the endpoint to use a custom marshaler.
Where does a sender endpoint fit into a solution?
Sender endpoints play the role of provider from the vantage point of the other endpoints in the ESB. As shown in Figure 3.1, “Sender endpoint”, a sender endpoint receives messages from the NMR and writes the message data to the file system.
Figure 3.1. Sender endpoint
![sender endpoint in a message exchange](https://access.redhat.com/webassets/avalon/d/Red_Hat_JBoss_Fuse-6.0-Using_the_File_Binding_Component-en-US/images/2e89b034881c9b92fdbfa4e632c8c04f/sender.gif)
Configuration element
Sender endpoints are configured using the
sender
element. All its configuration can be specified using attributes of this element.
Configuring a sender endpoint to use custom marshalers require the addition of other elements. These can either be separate
bean
elements or child elements of the sender
element.