org.mule.model
Class DynamicEntryPointResolver

java.lang.Object
  extended byorg.mule.model.DynamicEntryPointResolver
All Implemented Interfaces:
UMOEntryPointResolver

public class DynamicEntryPointResolver
extends java.lang.Object
implements UMOEntryPointResolver

DynamicEntryPointResolver is similar to the NonVoidEntryPointResolver except it also allows for void entry point s to be used. void entry points should be used with caution when leaving event dispatching to the descretion of the Mule Server. If an event is processed by a component and no return type is given, Mule will dispatch the previous event assuming any changes by the componentwould have been made to the previous event. In most situations thisbehaviour is fine, but there are circumstances where this is not suitable.

Version:
$Revision: 1.2 $
Author:
Ross Mason

Constructor Summary
DynamicEntryPointResolver()
          Default Constructor
 
Method Summary
protected  boolean isVoidOk()
          Determinse if a void Entrypoint can be accepted.
 UMOEntryPoint resolveEntryPoint(UMODescriptor descriptor)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

DynamicEntryPointResolver

public DynamicEntryPointResolver()
Default Constructor

Method Detail

isVoidOk

protected boolean isVoidOk()
Determinse if a void Entrypoint can be accepted. This will always return true for this implementation

Returns:
true

resolveEntryPoint

public UMOEntryPoint resolveEntryPoint(UMODescriptor descriptor)
                                throws ModelException
Specified by:
resolveEntryPoint in interface UMOEntryPointResolver
Throws:
ModelException


Copyright © 2003-2005 SymphonySoft Limited. All Rights Reserved.