Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.8)
  3. Reference
  4. Components
  5. Configuring Components

  6. Entry Point Resolver Configuration Reference

Entry Point Resolver Configuration Reference

Mule runtime engine version 3.8 reached its End of Life on November 16, 2021. For more information, contact your Customer Success Manager to determine how to migrate to the latest Mule version.

This page provides details on the elements you configure for entry point resolvers and entry point resolver sets.

Entry Point Resolver Sets

An extensible set of entry point resolvers. These determine how a message is passed to a component in Java. Each entry point resolver is tried in turn until one succeeds in delivering the message to the component. This element can be set on the model or component; the model value provides a default that individual component values can override.

Table 1. Child Elements of <entry-point-resolver-set…​>
Name Cardinality Description

abstract-entry-point-resolver

0..*

A placeholder for an entry point resolver element. Entry point resolvers define how payloads are delivered to Java code by choosing the method to call.

Legacy Entry Point Resolver Set

An extensible set of entry point resolvers (which determine how a message is passed to a component in Java) that already contains resolvers to implement the standard logic. This is already provided by default and is only needed explicitly if it needs to be extended with other entry point resolvers. This element can be set on the model or component; the model value provides a default that individual component values can override.

Table 2. Child Elements of <legacy-entry-point-resolver-set…​>
Name Cardinality Description

abstract-entry-point-resolver

0..*

A placeholder for an entry point resolver element. Entry point resolvers define how payloads are delivered to Java code by choosing the method to call.

Callable Entry Point Resolver

An entry point resolver for components that implement the Callable interface. This passes a MuleEventContext to the component. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Custom Entry Point Resolver

A custom entry point resolver. This allows user-supplied code to determine how a message is passed to a component in Java. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Table 3. Attributes of <custom-entry-point-resolver…​>
Name Description

class

An implementation of the EntryPointResolver interface.
Type: class name
Required: yes
Default: none
Table 4. Child Elements of <custom-entry-point-resolver…​>
Name Cardinality Description

spring:property

0..*

Spring-style property element for custom configuration.

Property Entry Point Resolver

Uses a message property to select the component method to be called. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Table 5. Attributes of <property-entry-point-resolver…​>
Name Description

acceptVoidMethods

Whether the resolver should call void methods. By default, void methods are not considered as possible candidates for message delivery.
Type: boolean
Required: no
Default: none

property

The name of the message property used to select a method on the component.
Type: name (no spaces)
Required: no
Default: none

Method Entry point Resolver

Delivers the message to a named method. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Table 6. Attributes of <method-entry-point-resolver…​>
Name Description

acceptVoidMethods

Whether the resolver should call void methods. By default, void methods are not considered as possible candidates for message delivery.
Type: boolean
Required: no
Default: none
Table 7. Child Elements of <method-entry-point-resolver…​>
Name Cardinality Description

include-entry-point

1..*

A possible method for delivery.

Reflection Entry Point Resolver

Generates a list of candidate methods from the component via reflections. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Table 8. Attributes of <reflection-entry-point-resolver…​>
Name Description

acceptVoidMethods

Whether the resolver should call void methods. By default, void methods are not considered as possible candidates for message delivery.
Type: boolean
Required: no
Default: none
Table 9. Child Elements of <reflection-entry-point-resolver…​>
Name Cardinality Description

exclude-object-methods

0..1

If specified, methods in the Java Object interface are not included in the list of possible methods that can receive the message.

exclude-entry-point

0..*

Explicitly excludes a named method from receiving the message.

Array Entry Point Resolver

Delivers the message to a method that takes a single array as argument. This element can be set on the model or component; the model value provides a default that individual component values can override. This element can also be used directly or as part of a set of resolvers; the resolvers in a set are used in turn until one is successful.

Table 10. Attributes of <array-entry-point-resolver…​>
Name Description

acceptVoidMethods

hether the resolver should call void methods. By default, void methods are not considered as possible candidates for message delivery.
Type: boolean
Required: no
Default: none

enableDiscovery

If no method names are configured, attempts to discover the method to invoke based on the inbound message type.
Type: boolean
Required: no
Default: true
Table 11. Child Elements of <array-entry-point-resolver…​>
Name Cardinality Description

exclude-object-methods

0..1

If specified, methods in the Java Object interface are not included in the list of possible methods that can receive the message.

exclude-entry-point

0..*

Explicitly excludes a named method from receiving the message.

include-entry-point

0..*

A possible method for delivery.

No Arguments Entry Point Resolver

Calls a method without arguments (the message is not passed to the component).

Table 12. Attributes of <no-arguments-entry-point-resolver…​>
Name Description

acceptVoidMethods

Whether the resolver should call void methods. By default, void methods are not considered as possible candidates for message delivery.
Type: boolean
Required: no
Default: none

enableDiscovery

If no method names are configured, attempts to discover the method to invoke based on the inbound message type.
Type: boolean
Required: no
Default: true
Table 13. Child Elements of <no-arguments-entry-point-resolver…​>
Name Cardinality Description

exclude-object-methods

0..1

If specified, methods in the Java Object interface are not included in the list of possible methods that can receive the message.

exclude-entry-point

0..*

Explicitly excludes a named method from receiving the message.

include-entry-point

0..*

A possible method for delivery.

Include Entry Point

A possible method for delivery.

Table 14. Attributes of <include-entry-point…​>
Name Description

method

The name of the method.
Type: name
Required: no
Default: none