Mule School: Introducing Mule 3.3 in Studio (Error Handling, Caching, Iterative Processing and Expressions) by Nial Darbey.
From the post:
Today I am going to introduce you to some powerful new features in Mule 3.3:
- Improved Error Handling: New exception strategy patterns fully integrated in Studio. Included are Try/Catch, Rollback processing and Conditional Exception processing in Choice routers based on exception type, or just about any criteria!
- Iterative Processing using Foreach Scope: Allows for iterative loop type processing while maintaining the original message context
- Mule Expression Language: A new, unified expression language to improve consistency and ease of use when validating, filtering, routing, or transforming messages
- Cache: Improve performance with “In memory” caching of messages, such as the results of service calls
- Graphical Data Mapper: A new graphical tool to easily transform from one data format to another data format while also mapping specific fields within the message structure. Formats supported include XML, JSON, CSV, POJOs, collections of POJOs, and EXCEL
We will do so by walking you through the development of a Mule Application which exploits each of these new features. As we work our way through the development process we will describe what we want to achieve and explain how to achieve that in Mule Studio. For the sake of simplicity we will refer you to our online documentation when we touch on features already available in previous releases.
I need to install the most recent release (Mule 3.3) but just walking through the post I stumbled at:
Graphical Data Mapper
….
Here we need to transform our OrderItem instance into an OrderRequest as expected by Samsung’s webservice.
The image that follows shows a mapping from:
name: string -> name: string
quantity: integer -> quantity: integer
But I didn’t see any naming of the OrderItem or OrderRequest objects?
Not to mention the mapping seems pretty obvious.
A more useful case of documentation would be “who” created the mapping and when? Even more useful would be the ability to define what caused the mapping from one to the other. Not just the fact of mapping.
Like I said, I will have to install the latest version and walk through the examples, so expect further posts on this release.
Your comments and suggestions, as always, are welcome.