Java Reference
In-Depth Information
To execute this new service, you would create a JAR file that contains the component class
and this configuration file and then put that JAR in Mule's lib/userdirectory so that it's avail-
able on the classpath when Mule starts.
If you want to create a transformer for a message flow, you would write a class that extends
org.mule.transformer.AbstractTransformer
, and then point to this class in the
<in-
bound>
or
<outbound>
route of the
<service>
in mule-config.xml.
Obviously, the point here is not to give you a Mule tutorial; I'm only trying to illustrate what
the programming model is like so that you'll have an idea of how your days will be spent if
you use Mule. In short, you'll be writing Java code and XML to do the hookups, and you'll
need to code directly against the Mule API.
MuleForge
Mule is popular and has many of the basic features of a commercial ESB, but it doesn't come
in a slick package or have a particularly friendly interface. Instead of dragging and dropping
to create a new route, developers must write against the API directly. The website's document-
ation is slight, but developers are encouraged to check out the MuleForge community site at
MuleForge hosts a wide array of developer projects that support different transports (including
Hibernate, Hl7, JIRA, JXTA, TIBCO Rendezvous, and others). Developers contribute visual-
izers, dashboards, and other items to enhance the Mule development experience. At this point,
many of these projects are simply proposals, or are in an alpha or pre-alpha stage.
Supported transports
Mule also supports a wide variety of transports, including the following:
▪ JMS
▪ File
▪ FTP
▪ HTTP/S
▪ IMAP
▪ JDBC
▪ SOAP
▪ POP3
▪ Remote EJB
