|Home >> All >> org >> [ mule Javadoc ]|
|||org.mule.digester.* (5)||||org.mule.mules.* (1)||||org.mule.providers.* (26)|
|||org.mule.test.* (21)||||org.mule.transaction.* (4)||||org.mule.transformers.* (10)|
|||org.mule.umo.* (35)||||org.mule.util.* (22)|
org.mule: Javadoc index of package org.mule.
org.mule.umo.transformer: The Universal Message Object(tm) API provides a way for components to interact without needing to know about the protocol or delivery mechanisms of information passed between them
org.mule.digester.converters: Contains the classes necessary to process the mule-config.xml with Digester
org.mule.providers.vm: Contains Abstract classes providing common functionality for all mule providers
org.mule.util: Defines the main public API of the MuleManager and support classes
HttpConnector: HttpConnector provides a way of receiving and sending http requests and responses. The UMOConnector itself handles dispatching http requests. The HttpReceiver handles the receiving requests and processing of headers This connector recognises the following properties - transport.http.hostname - The hostname to send and receive http requests transport.http.port - The port to listen on. The industry standard is 80 and if this propert is not set it will default to 80 transport.http.proxyHostname - If you access the web through a proxy, this holds the server address transport.http.proxyPort - The port ...
UMOTransformer: UMOTransformer manages the transformation and or translation of one type of data to the other. Source data is received, then processed and returned via the transform() method. The return Class is specifed so that the return message is validated defore it is returned. This interface also has the provission of a Transformer session, which simply keeps a copy of the 'live' transfromed data, so that any further transformations will use this cached data. When a session is rolled back a cached copy of the source data will be returned. When the session is committed the caches are cleared. Starting a session ...
UMOMessageReceiver: UMOMessageReceiver is used to receive data from an external system. Typically an implementation of this interface will also implement the listener interface for the external system. For example to listen to a JMS destination the developer would also implement javax.jms.MessageListener. The connector (which creates the UMOMessageReceiver) will then register the reciever with the JMS server. Where a listener interface is not availiable the derived UMOMessageReceiver will implement the code necessary to receive data from the external system. For example, the file connector will poll a specified directory ...
AbstractConnector: AbstractConnector provides base functionality for all connectors provided with Mule. Connectors are the mechanism used to connect to external systems and protocols in order to send and receive data. The AbstractConnector provides getter and setter methods for connector properties, name, transport name and protocol. It also provides methods to stop and start connecotors and sets up a dispatcher threadpool which allows deriving connectors the possibility to dispatch work to separate threads. This functionality is controlled with the transport.connector.doThreading property.
MuleEvent: MuleEvent represents any data event occuring in the Mule environment. All data sent or received within the mule environment will be passed between components as an UMOEvent. The UMOEvent holds some data and provides helper methods for obtaining the data in a format that the receiving Mule UMO understands. The event can also maintain any number of properties that can be set and retrieved by Mule UMO components.
UMOEvent: UMOEvent represents any data event occuring in the Mule environment. All data sent or received within the mule environment will be passed between components as an UMOEvent. The UMOEvent holds some data and provides helper methods for obtaining the data in a format that the receiving Mule UMO understands. The event can also maintain any number of properties that can be set and retrieved by Mule UMO components.
MuleManager: MuleManager maintains and provides services for a Mule instance. All mules and tranformations are registered in the MuleManager. The Transaction Manager and performance metric helpers is also accessible from here. The developer can use the Mulemanager to stop start or pause all or any specific mules in the system.
Application: Application is a strategy class which can be implemented to do some application specific work when the MuleManager is initialising. The initialise method is called after all global configuration has been loaded but before the mule-descriptor configurations are loaded.
MuleFactorySupport: MuleFactorySupport is a factory for creating UniversalMessageObject instances. The MuleFactorySupport class performs all the common functions necessary to create and initialise a MuleUMO. Specific MuleUMO instances must have a factory class that should extend this hsupport class.
MuleRuntimeException: MuleRuntimeException Is the base runtime exception type for the Mule Server any other runtimes exceptions thrown by Mule code will use or be based on this exception. Runtime exceptions in mule are only ever thrown where the method is not declared to throw an exception and the exception is serious.
UniversalMessageObject: UniversalMessageObject describes the methods for a Universal Message Object. It provides methods for initialisation, dispatching, sending, and creating events. The UniversalMEssageObject interface implements the UMOChain interface so that other UMOChain implementations can be chained to it.
UMOSyncChainSupport: UMOSyncChainSupport is used to provide UMOs with an interface that supports synchronous message calls. This interface is not included with the UMOChain interface to avoid the need to implement both async and sync method calls when only async calls are being used.
MuleMessageAdapter: MuleMessageAdapter provides a common abstraction of Mule Event message. The message adapter allows a Mule event to be read and manipulated like any other object data type from any external system that has a Mule provider implementation.
GZipCompression: GZipCompression a CompressionStrategy implementation using the GZip library included in the JDK java.util.zip. This is the default CompressionStrategy used by the CompressionHelper discovery when no other implementation is discovered
TestingMule: TestingMule is a Test harness Mule implementation which can be used to ease the development of Unit test cases. This Mule can be instanciated from a constructor, that can be manipuated outside of the mule manager
IteratorAdapter: Utility method for converting Enumeration to an Iterator class. If you attempt to remove() an Object from the iterator, it will throw an UnsupportedOperationException. Added for use by TagLib so Enumeration can be supported
JMSTransformer: JMSTransformer is an abstract class the should be used for all transformers where a JMS message will be the transformed or transformee object. It provides services for compressing and uncompressing messages.
MuleConstants: MulePropertyConstants contains any global, Mule specific constants This is more than likely a temporary class that will be removed in favour of having all constants contained in the classes that use them.
AbstractTransformer: CompressionTransformer Is a base class for all transformers. Transformations transform one object into another. This base class provides facilities for compressing and uncompressing messages.
CompressionTransformer: CompressionTransformer Is a base class for all transformers. Transformations transform one object into another. This base class provides facilities for compressing and uncompressing messages.
DefaultExceptionStrategy: DefaultExceptionStrategy Provides a default exception handling strategy. The class final thus to change exception handling behaviour the user must reimplemented the ExceptionListener Interface
EventTimerTask: EventTimerTask is a task that causes TimeEvent to be fired to listening objects when a specific number of milliseconds have passed. This implementation is based on the java.util.TimerTask.
SimpleMuleChain: SimpleMuleChain encapsulates the lowest execution object for a Universal Message Object By implementing this interface an objects can be linked together into an execution chain.
ProviderList: ProviderList encapsulates two lists of ProviderDescriptors; send providers and receive providers. It also provides helper methods to query manipulate and maintain state of the lists.
AbstractMessageReceiver: AbstractMessageReceiver provides common methods for all Message Receivers provided with Mule. A message receiver enables a connector to receive a message from an external system.