projects
Send and receive Mule Messages to/from a 3270 session.
Abdera is an Apache project which implements the Atom Publishing Protocol. This project will make it easy to expose APP services as a mule component.
A connector that will allow mule to seamlessly interact with Amazon SQS, similar to a jms queue.
Documentation and in depth description is here:
http://urlx.org/amazon.com/9ca37
A set of annotations for configuring Mule at various levels such as services, endpoints, entry points and routers. These annotations offer an alternative to configuring Mule from Xml or programmatically.
A Mule Filter implementation which scans payload of mule messages for viruses. This filter will make use of an underlying Virus scanning engine like F-Secure, Kaspersky, ClamAV etc).
This transformer takes a byte array or string as the input source and transforms it into a byte array in one of the FOP formats.
AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.
This transport module caters to the need.
The Data Area is like a plain text file but in AS400. It's created with an specific length. Many AS400 System use this Data Areas to show systems or process stay because it is very easy to access from Cobol/400 and RPG/400 programs.
AS400 Data Queue Transport
Connector providing real time integration with the Asterisk open source PBX.
http://developer.37signals.com/basecamp/ refers to simple HTTP requests that
can interact with BaseCamp. We could theoretically integrate, say, Outlook
and BaseCamp using Mule or perhaps have an "automatic download from B/Camp"
option using Mule.
It would be nice to abstract the Message types and URIs from the user so you could do something like -
basecamp://ross:${mypassword}@createComment?postId=1
Ideally, we'd want to get the 'postId' from the message i.e.
basecamp://ross:${mypassword}@createComment?postId=${bean:message.postId}
This will only be possible in Mule 2 though...
Also, you could configure the server details on the BasecampConnector, like we do with the SF connector.
An Mule example that demonstrates how to process batch files by splitting them into individual entries. The example will also demonstrate using the following: Scripting, orchestration, RESTPack (Jersey, Abdera), Writing to MySQL and using expressions.
Mule CICS CTG Transport provides a connectivity to a mainframe CICS application via IBM CICS Transaction Gateway(CTG). It provides XML ,SOAP/WSDL and REST interface for Mule client.
It transforms Mule client message to CICS commarea message using XML schema. XML schema is generated by a tool using cobol copybook.
This project is to provide a transport to allow files to be registered with or checked against Codel, using their Codel Mark.
The Common Retry Policies is a module containing community built and maintained implementations of retry policies.
corba is still widely used in enterprise. This project is to provide a transport mechanism for mule component to connect to corba services running in different ORBs (orbix, visibroker, websphere, etc) and expose/publish mule services as corba services
An example project that demostrates how to use Mule to process financial data such as SWIFT, FIX and ISO20022 using Volante and Artix DS.
EDIReader MuleKit is a set of Mule transformers and routers that provide flexible handling of EDI data with Mule. The MuleKit is build upon EDIReader, a proven open source Java framework for parsing EDI data in a way that allows simple integration with XML tools. The combination of Mule and EDIReader in this manner offers a rich variety of options for configuring EDI solutions with Mule in the same ways that you configure XML processing.
Mule EJB provider can only invoke EJB 2.x methods.
EJB 3.0 changed the way in which you obtain the reference to the remote EJB.
This provider supports invoking EJB3.0 methods.
Example: <endpoint address=\"ejb3://localhost:3700/org.me..SLSBEchoRemote?method=echo\"/>
Integration between Mule and Esper, the open source CEP engine. This would allow Esper to process Mule events and allow Mule processes to be triggered by Esper events. For more information about Esper see: http://esper.codehaus.org.
This module concentrates on Excel-Support by providing services to read and write excel files. As a starting point a simple mule module was developed which can write excel sheets by using http://jxls.sourceforge.net/. There is also a simple transformer with a mapping (in order to map excel to beans) when reading excel file.
Further discussion see: http://www.nabble.com/New-MuleForge-project-%28Excel%29-to16114555.html#a16116737
Exec provider, which executes external processes, based on Apache Ant Execute taskdef and inheriting all the features.
To provide support for scripting languages such as Ruby, JavaScript, Python, and more. (Groovy is already supported by Mule.)
This project will add extended XML support to Mule by adding additional XML data binding frameworks as outlined in http://mule.mulesource.org/jira/browse/MULE-1208.
The Flatfiles Support project.
Mule Galaxy is an open source governance platform with an integrated registry/repository. It includes versioning, lifecycle management, dependency management and policy enforcement features which enable you to effectively govern your applications and services. Support for a wide range of products is included, including support for Mule, Apache CXF, Spring and Maven. Custom integration may also be written via Galaxy's simple Atom Publishing Protocol HTTP API.
The GeoMail application listens for incoming emails from your e-mail account. For each received e-mail, the originating senders IP-address is extracted and an external Web Service is used to resolve that IP-address into a Geographic location. This information is then used to display, in a Google Map, how geographically spread you e-mail correspondance is.
GeoMail can, for example, be used by Open-Source projects to visualize how widespread its mailinglist subscribers are.
Currently the mule http.servet classes are based on http GET and POST calls. However, modern web applications depend strongly on AJAX technology. The Google Web Toolkit (GWT) is one framework available that allows development of both server and client sides code with Java, and uses remote procedure calls to wrap AJAX connections. Client side java is translated into JavaScript, ether during runtime to allow for debugging or before execution to increase speed.
This project would house a series of classes that could facilitate incorporating mule into web applications made with the Google Web Toolkit. Because GWT is written in Java 1.4, code from the mule tree could actually be exicuted by the web client. Or the mule layer could remain on the server allowing the web application to be mule independent.
Provides support for instantiating Java classes through Guice.
Connector for getting / putting files into the Hadoop distributed file system.
This transport uses the Hessian object serialization protocol. The goal is to be able to send messages to Mule using a Hessian client (e.g. using Spring remoting) and also to be able to dispatch from Mule to a remote Hessian service. Internally the transport uses the Apache MINA package to handle TCP streaming.
Provides support for data object management using the Hibernate object-relational mapping API.
Provides extensions to use HiveMind with Mule, such as using the container as a factory for Mule managed objects.
MLLP is widely used in healthcare settings.
参加メンバー募集中！
ESB Muleの日本語化とドキュメントを作成します。
英語のESB Muleページや資料を翻訳するだけではなく、より多くのユーザにESB Muleを使っていただくために、新規に作成された日本語の資料も公開していきます。
ESB Muleの日本語ドキュメントを参照するには、
左メニューから「Project Wiki」を選択し、表示されたページ内の「ホームページ」をクリックしてください。
本プロジェクトは、Mule及び関連ソフトウエアを日本語環境で円滑に利用できるようにプログラムをI18N及びL10Nすることを目的とします。
Transport that provides connectivity to Jaspersoft
JavaSpaces integration package
Can bind to a JBI container allowing components to send events via Mule.
The current version supports JCR 1.0 containers.
Allows Mule to consume and dispatch data events to JDEdwards applications using GenJava Api.
A transport which supports JAX-RS services using Jersey.
Transport and functionalities to integrate with Atlassian JIRA -- The enterprise issue tracker.
The JMX transport allows mule components to invoke operations, get/set attributes and receive notifications from MBeans residing in remote or embedded MBeanServer.
Can be used together with Quartz transport to implement session schedules by invoking start, stop, connect and disconnect in the mule componnent's MBeans. Also, can be used as a way to shutdown the Mule server in response to a remote event.
Implementation of JSON transformers for Mule so that objects can be serialized and deserialised using JSON object notation. There is a project called Jackson (jackson.codehaus.org) that should be used for the the actual serialization since it supports streaming and should fit well with Mule.
This project will implement the JXTA p2p protocol, most importantly for peer discovery and firewall/nat bypassing.
Provides support for connecting directory services via ldap/ldaps.
Based on jldap developed by openladap/novell. See http://www.openldap.org/jldap/
Legacy IBM CICS integration for Mule based on open-source LegStar (http://www.legsem.com/legstar).
This is some work I've been doing on provider and dispatcher functionality with Lingo for Mule. The source code as well as a binary snapshot are available here, along with provider and dispatcher examples. Please consider this code extremely alpha as its my first attempt at mucking with Mule's internals; it seems stable in my environment but i have yet to test extensively.
A transport to send and receive Mule Messages to/from a Lucene index.
This project is used to track the support of AMQP in Mule. This is not an AMQP implementation but does provide information about AMQP implentations that support Mule as a client.
This is part of the regular build at the moment but should be moved out of the regular build as it causes trouble.
Mule "Clustering" via replacement of internal VM Queues with JMS Queues
This is the example application that was
created for the Mule-related InfoQ
article 'Using SEDA to Ensure Service
Availability' by Rune Schumann and Rune
Peter Bjørnstad.
As part of our performance tuning initiative, we're building a maven archetype that creates a new maven module used for performance benchmarks.
This project will allow JCA connectors to work directly with Mule.
This module provides security configuration within mule based on SAML (www.opensaml.org). Besides a security provider for SAML, various authentication handlers for exiting transports are provided
This project consists in the Netbeans Plugin for Mule ESB development with the objective to facilitate and to guide the construction of the config.xml archives using the Netbeans IDE Code Snippets.
We've already initiated the construction of this project and some sources already can be submitted for evaluation or demonstration.
Provides a non-blocking socket transport for Mule. This project uses the Mina project and support nio for TCP and UDP.
Mule Spring Proxies makes it possible to configure and inject a Mule proxy using Spring configuration as a Springified alternative to MuleClient. The module might be a part of the SMuT Stack and simplifies interaction between services outside Mule and Mule services (UMOs). Attached so far is a simple poc.
This is a plugin I wrote to integrate the new test exclusion mechanism into the Maven site.
Allows Mule to seamlessly host standard Java Web Applications (integrated Jetty 6). Packed/exploded deployment, re-deployment and hot-deploy of apps available.
Mule integration for the Intel® XML Software Suite and SOA Security Suite
Adds Oracle-specific functionality to the standard Mule JMS transport. OracleAQ is a JMS implementation which uses the Oracle RDBMS for message persistence.
OpenSymphony's OSWorkflow (http://www.opensymphony.com/osworkflow) is a simple FOSS workflow engine, similar to jBPM. It has a nice clean API which makes it straightforward to integrate with Mule via the BPM transport.
Provides extensions to use PicoContainer with Mule, such as using the container as a factory for Mule managed objects.
A container context that allows Mule
objects to be configured using Plexus
or have Plexus services managed by
Mule.
A transport for Rabbit MQ.
A Restlet transport for Mule (http://restlet.org).
This example employs the Routing Slip pattern, as described in Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf, and demonstrates how this example can be implemented using Mule framework.
RSS Mule support
The SalesForce Transport uses Mule to enable powerful, seamless integration between Salesforce and other enterprise systems.
This project is to provide support to the process of introducing SCA support into Mule.
S2Mule helps Java developers to use Mule's very significant functionalities from Seasar2 applications easily. Java developers are able to configure S2Mule by dicon file only. So, They don't need to learn XML configuration syntax any more.
This project deals with wrapping Serving XML in a transformer to be able to use Serving XML and all its power inside Mule.
Related Mule-JIRA Issue:
http://mule.mulesource.org/jira/browse/MULE-1262
The latest version for Serving XML can always be downloaded here: http://servingxml.sourceforge.net/
The SFTP Transport uses the Java Secure Channel (JSCH) library to transfer file messages to and from an external SFTP service.
A simple component that generates an HTML dashboard representing event flows in a single Mule instance, as shown here:
http://ddossot.blogspot.com/2008/04/not-dash-bored.html
Smooks is a Java Framework/Engine for processing XML and non XML data (CSV, EDI etc). It can be used to perform Data Transforms using existing Transformation and Templating technologies such as XSLT, FreeMarker, StringTemplate etc. Smooks can also be used to simply analyze a data stream - e.g. to populate a Java Object model from the data stream (CSV, EDI, XML etc). Smooks supports both DOM and SAX processing models, but adds a more "code friendly" layer on top of them. It allows you to plug in your own "ContentHandler" implementations (written in Java or Groovy), or reuse some existing handlers. For more information about Smooks see http://milyn.codehaus.org/Smooks
Main objective of this project is to develop a transport provider to link the SMSPP (Short Message Peer to Peer) messaging protocol to MULE. This protocol mainly work like TCP socket application. One side connects to a short message center (SMSC) and the other end connects to an IT system or MIS or any information processing application.The IT systems do not know about how to process telecom protocols so mule can translate it as SOAP or any other known message formats by using SMPP transport. Current Implementation sticks with SMPP 3.1 but it can be pluggable.
Transport-smtpin allows you to receive e-mail without any additional infrastructure. E-mails are received directly with the SMTP protocol.
Transport-smtpin uses the SubEthaSMTP Mail Server (the last freaking java SMTP implementation) for the hard work.
A module to connect to the sugarCRM application.
This module implements SWIFT FIN parsing and validating the SWIFT input to produce a detailed validation report ( Validation includes Network Validation Rules)
A plugin for SXC - a streaming XML compiler - which supports streaming XPath. This will allow messages to be routed by XPath expressions as efficiently as possible.
Provides Tibco Rendezvous connectivity for Mule. An inbound/outbound rendezvous transport supporting: certified messaging, distributed queues, runtime defined endpoints, etc.
This transport enables file messages to be sent over file channel supported by Apache VFS.
A tool for generating visual representations of Mule's XML configuration files.
Legacy support for WebMethods Glue integration. This was supported in Mule up until Mule 1.4. The code and docs are available here in case there is someone in the community that is willing to port it to 1.4/2.0.
The aim of this project is to extend WSDL SOAP mule transport in order to integrate Grid Globus Service (GT4 Globus Alliance org) on Mule.
This project will host the ws-security module from the current mule-2.0.x branch.
Send mule messages to XAware composite data services (see xaware.org).
General News