The MuleSoft Developer community is a place where you, integration professionals, can connect online and offline, expand your knowledge, and build your career. The MuleSoft Developer community is also a place where you can exchange best practices, share knowledge with others, and network with the best Mule developers across the world.
Here’s the new edition of our monthly blog highlighting great contributions from MuleSoft Developers who share great knowledge with our community. March was a great month, and we want to share some of the amazing work we’ve seen across the community.
Earlier this year, we started a new blog series, highlighting great contributions from MuleSoft Developers that are willing to share knowledge with the community. February was another busy month for Mule developers, and we want to share some of the amazing work they have been doing for the community.
We are lucky to have some great contributors in the MuleSoft community. And we’d like to highlight the things they do to make our community so fantastic. From the forums to in-person events and video tutorials, we see great community contributions from MuleSoft Developers willing to share their knowledge with others. Today, we want to recognize the great work of MuleSoft Developers in January 2018 and share it with you.
In my last post, I discussed DataWeave 2.0 header and body (iterative functions) changes in Mule 4 Beta. In this post, I will dive deeper into the topic by discussing operator changes (within the body) as well as other changes.
The long-term success of a technology ultimately lies on the strength of its community. At MuleSoft, we are fortunate to have a vibrant community that has many members who contribute by answering questions, sharing best practices, and organizing meetups. Their knowledge and effort made the experience of building solutions with MuleSoft simpler and more rewarding.
This post was written by one of the stars in our developer community, Kian Ting. Read this post to learn how to use a Mule app to retrieve legacy data and sync it to a new destination endpoint with the poll scope method.
As integration developers, we are always faced with the need to poll a legacy resource to retrieve new data and to sync it over to another destination endpoint.
Mule 4 beta is already out. One of the major change in Mule 4 is making DataWeave a default expression language over Mule 3’s default Mule Expression Language (MEL). The XML namespace of DataWeave is moved from dw to ee (core), and the DataWeave version has changed from 1.0 to 2.0 in Mule 4.
The MuleSoft Champions Program is our developer advocacy program designed to provide support, networking opportunities, and recognition for MuleSoft developers all around the world. Joining the Champions Program can also have a positive effect on your career. But what it can also do is give you an opportunity to get free MuleSoft training!
Members of the Champions Program complete challenges to get points, and those points can be exchanged for MuleSoft training courses.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.