DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • A Spring Boot App With Half the Startup Time
  • Improving Java Application Reliability with Dynatrace AI Engine
  • A Systematic Approach for Java Software Upgrades
  • Building a Simple RAG Application With Java and Quarkus

Trending

  • Building Multi-Rail Payment Failover to Stop Latency Spikes and Double Debits
  • From Issue to Reviewable Patch: Build a Sandboxed Coding Agent With Deep Agents and Automated Tests
  • Building a Real Pipeline With senro: Monorepos, Caching, and Triggers
  • Engineering Data Observability: Detecting Schema Drift, Data Drift, and Silent Pipeline Failures

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Software Design and Architecture
  3. Integration
  4. Mule 3.8-9: Run Java Method on MuleSoft Application Startup

Mule 3.8-9: Run Java Method on MuleSoft Application Startup

This article explains how to execute a Java method once or on MuleSoft Application Startup.

By 
Enrico Rafols Dela Cruz
·
Sep. 28, 18 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
9.4K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

In this article, I will explain how to execute a Java method once or on Mulesoft Application Startup. With this approach, we can add or execute some needed tasks before a Mule Application fully deployed such as User Notification or Data Clean-Up (Truncation of Database Tables or purging of files from the temporary storage within the server).

First, we need to create a Custom Java Class that implements the interface MuleContextNotificationListener<MuleContextNotification> and override the onNotification() method. We also need to make sure that our startup logic should run after the Mule Context started.

Custom Java Class:

package com.startup;

import org.apache.log4j.Logger;
import org.mule.api.context.notification.MuleContextNotificationListener;
import org.mule.context.notification.MuleContextNotification;

public class StartupRunner implements MuleContextNotificationListener<MuleContextNotification> {

    private static final Logger LOG = Logger.getLogger(StartupRunner.class);
    private final String MULE_CONTEXT_EVENT_STARTED = "mule context started";

    @Override
    public void onNotification(MuleContextNotification notification) {
      if (notification.getActionName() == MULE_CONTEXT_EVENT_STARTED) {
          LOG.info("################## MY STARTUP JAVA LOGIC ##################");
          LOG.info("################## ENRICO RAFOLS DELA CRUZ ##################");
          LOG.info("######## EVENT: "+notification.getActionName()+" ##########");
      }
    }
}

Mule Configuration:

Create a Spring Bean for the above Custom Java Class and reference it to the Mule Notification. We need to use the below Mule Notification to enable the event listener for the Mule Context.

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
xmlns:spring="http://www.springframework.org/schema/beans" version="EE-3.9.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd">

    <spring:beans >
        <spring:bean name="startupListener" class="com.startup.StartupRunner" />
    </spring:beans>

    <notifications>
        <notification event="CONTEXT" />
        <notification-listener ref="startupListener" />
    </notifications>

    <flow name="flow-execute">
        <poll doc:name="Poll">
            <fixed-frequency-scheduler frequency="20" timeUnit="SECONDS"/>
            <logger message="Start Flow" level="INFO" doc:name="Logger"/>
        </poll>
        <logger level="INFO" doc:name="Logger" message="End Flow"/>
    </flow>

</mule>

Testing:

On deploying the Mule Application, we can see that the Custom Class com.startup.StartupRunner executed once during the Mule Application startup.

Image title

That's it. Hope this helps! Let me know of any thoughts or questions you might have by asking in the comments section.

application Java (programming language) MuleSoft

Opinions expressed by DZone contributors are their own.

Related

  • A Spring Boot App With Half the Startup Time
  • Improving Java Application Reliability with Dynatrace AI Engine
  • A Systematic Approach for Java Software Upgrades
  • Building a Simple RAG Application With Java and Quarkus

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook