org.mule.module.extension.internal.runtime.resolver

Class ResolverSet

java.lang.Object

org.mule.module.extension.internal.runtime.resolver.ResolverSet

All Implemented Interfaces:

ValueResolver<Object>

public class ResolverSet
extends Object
implements ValueResolver<Object>

A ValueResolver which is based on associating a set of Parameters -> ValueResolver pairs. The result of evaluating this resolver is a ResolverSetResult.

The general purpose of this class is to repeatedly evaluate a set of ValueResolvers which results are to be used in the construction of an object, so that the structure of such can be described only once (by the set of Parameters and ValueResolvers but evaluated many times. With this goal in mind is that the return value of this resolver will always be a ResolverSetResult which then can be used by a ObjectBuilder to generate an actual object.

Instances of this class are to be considered thread safe and reusable

Since:

3.7.0

Constructor Summary

Constructors

Constructor and Description
ResolverSet()

Method Summary

Methods

Modifier and Type	Method and Description
ResolverSet	add(org.mule.extension.introspection.Parameter parameter, ValueResolver resolver) Links the given ValueResolver to the given Parameter.
Map<org.mule.extension.introspection.Parameter,ValueResolver>	getResolvers()
boolean	isDynamic() Whether at least one of the given ValueResolver are dynamic
ResolverSetResult	resolve(MuleEvent event) Evaluates all the added ValueResolvers and returns the results into a ResolverSetResult

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ResolverSet

public ResolverSet()

Method Detail

add

public ResolverSet add(org.mule.extension.introspection.Parameter parameter,
              ValueResolver resolver)

Links the given ValueResolver to the given Parameter. If such parameter was already added, then the associated resolver is replaced.

Since this class implements Lifecycle and MuleContextAware, this method works in tandem with the ones defined in that interface. All the lifecycle invocations received by this instances are propagates to the registered resolvers. You should make a best effort then to add all the resolvers before lifecycle is applied. Otherwise, adding more resolvers will be allowed but you'll be in charge of whatever lifecycle phases it has missed

Parameters:

parameter - a not null Parameter

resolver - a not null ValueResolver

Returns:

this resolver set to allow chaining

Throws:

IllegalArgumentException - is either parameter or resolver are null

isDynamic

public boolean isDynamic()

Whether at least one of the given ValueResolver are dynamic

Specified by:

isDynamic in interface ValueResolver<Object>

Returns:

true if at least one resolver is dynamic. false otherwise

resolve

public ResolverSetResult resolve(MuleEvent event)
                          throws MuleException

Evaluates all the added ValueResolvers and returns the results into a ResolverSetResult

Specified by:

resolve in interface ValueResolver<Object>

Parameters:

event - a not null MuleEvent

Returns:

a ResolverSetResult

Throws:

Exception

MuleException

getResolvers

public Map<org.mule.extension.introspection.Parameter,ValueResolver> getResolvers()