Notifier API Updated for Payara Server Community Edition

Jakarta EE

Previously, Payara Server did not offer a convenient way to add extensions. If you wanted to add an extension, you had to download the Payara Server code base, build the entire repository, write your own extension and module, and basically act as a developer. We’re working to create a simplified way to add extensions to Payara Server, starting with the Notifier API. 

The notification service received a major overhaul in Payara Server Community 5.2020.5 (October 2020) that makes implementing new notifiers in a modular fashion easier. The overhaul also involved rewriting the existing notifiers as extensions, porting them over to a new community repository, and then implementing new Discord and Microsoft Teams notifiers. 

Since this is quite a large change, we’re rolling it out in Payara Server Community Edition first to ensure it is fully stable before moving it into Payara Enterprise. 

The Notifier API is now an extension you can implement in a simplified way.  Community users can drag and drop any JARs uploaded to our new public Nexus repository into their Payara installation, or grab the code from the new Payara Notifiers Nexus Repository to build the JARs themselves

A few notifiers will still ship as default with Community, including Event Bus, CDI Event Busand JMS notifiersYou can still disable them if you choose. If you had notifiers configured previously and you upgrade to Payara Server Community 5.2020.5, you will receive a warning message as you need to reconfigure the notifiers. 

If you upgrade from Payara Community to the Enterprise Edition, your notifiers will continue to work without any further action on your part. 

Payara Server Enterprise customers have access to notifiers which are stable included automatically and with out-of-the-box functionality. As new notification channels become stable in the Payara Server Community Edition, we will add them to Payara Enterprise.  

Payara developers see this notification system overhaul as a building block for future development. For example, this sets the stage for a potentially adding functionality to the Payara Enterprise Administration Console to easily add and remove extensions to your environment without having to configure everything manually. 

We’d love to know what the community thinks of the new Notifier API and get your feedback about how it’s working for you and updates you’d like to see in future releases.  

Comments (0)

Post a comment

Your email address will not be published. Required fields are marked *

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Posts

Blue background with coral and fish. Left text: 'MONTHLY CATCH'. Right: laptop screen with tech tabs and Payara Community logo. 5 minutes
Community

The Payara Monthly Catch – November 2025

November has been one of the busiest months of the year for the Java and Jakarta EE ecosystem. With […]

Payara promotional graphic for Jakarta Data, featuring and illustrated server stack labeled Core, Web, Full Platform. 3 minutes
Community

Jakarta Data Makes Persistence a Breeze 

Working with enterprise Java databases can sometimes feel like swimming upstream. Jakarta EE 11’s Jakarta Data helps developers glide […]

Green stylised leaf symbol representing the Spring Framework, shown with a smooth curved shape and a small stem inside a circular or rounded background , with 'spring' written on its right side. 2 minutes
Jakarta EE

Spring Framework 7.0 and Spring Data 2025.1.0 Embrace Jakarta EE 11 Compatibility

The recent releases of Spring Framework 7.0 and Spring Data 2025.1.0 mark an important milestone for the Java ecosystem, […]