Mule : Sandbox
This page last changed on Apr 19, 2006 by tcarlson.
The sandbox is a staging area for Mule components, extensions and sub-projects. They are located and developed in the sandbox until they are considered production ready, then they are shipped with the Mule distribution. Sandbox projects are located in Subversion. To use a sandbox project you will need to -
What's in the SandboxYou can browse the sandbox repository here. The components in the sandbox are listed below. Spring's HttpInvokerSupport for using Spring's HttpInvoker to export services. Starting Mule from within SpringClasses for bootstrapping Mule from within Spring. VFS Transport ProviderEnables access to and from various protocols such as WebDav, Samba, File System, Jar/Zip and more. This transport needs a little work to get included in the Mule distribution. Vendor ExtensionsContains patches and enhancements need to get some commercial and open source projects to work with Mule. A patch is usually written only if the Vendor implementation doesn't implement a specification correctly causing unexpected behaviour when used with Mule. IBM MQeThe IBMMqeConnector is a replacement for the standard jms connector to be used with IBM MQe. What has graduated from the SandboxAS400 Data Queue TransportThis transport provider allows your components and services to send and receive messages from IBM's AS400 Data Queue server. For more information see Configuring AS400 DQ and Mule. Oracle Advanced QueuingOracle support has now been given its own Module. See Oracle AQ Integration for details. Deprecated ComponentsDeprecated components are extensions to Mule that no longer ship with the Mule distribution, usually because there is a better implementation that now ships with Mule. These components are no longer maintained.
|
![]() |
Document generated by Confluence on Oct 03, 2006 09:23 |