Custom filters in MuleSoft allow developers to implement their own filtering logic by creating classes that implement the Filter interface. These custom filters can then be used with the <custom-filter> element, specifying the class and any configuration properties. For example, a custom filter could check for a specific request URL pattern and only allow messages that match.

1. Custom Filters in MuleSoft

2. Custom Filters
• The standard filters handle most filtering
requirements, but you can also create your
own filter. To create a filter, implement
the Filter interface, which has a single
method:
public boolean accept(MuleMessage message);

3. • This method returns true if the message
matches the criteria that the filter imposes.
Otherwise, it returns false.
• You can then use this filter with the <custom-
filter...> element, using the class attribute to
specify the custom filter class you created and
specifying any necessary properties using
the <spring:property> child element.

4. For example:
• <outbound> <filtering-router> <http:outbound-
endpoint
address="http://localhost:65071/services/EnterO
rder?method=create" exchange-
pattern="request-response"/> <custom-filter
class="org.mule.transport.http.filters.HttpReques
tWildcardFilter"> <spring:property
name="pattern"
value="/services/EnterOrder?wsdl"/> </custom-
filter> </filtering-router> </outbound>

5. • A user-implemented filter.
• Attributes of <custom-filter...>
Name
• Identifies the filter so that other elements can
reference it. Required if the filter is defined at the
global level.
class
• An implementation of the Filter interface.

6. • Child Elements of <custom-filter...>
spring:property
• Spring-style property element for custom
configuration