Smooks Data Integration
The official blog
0
Two of the main new features in Smooks v1.4 are, out of the box support for UN/EDIFACT Interchanges, and Apache Camel integration.
The new UN/EDIFACT support allows you to process UN/EDIFACT Interchanges by either or both of the following methods:
- Conversion to XML, allowing you to use standard XML tools (or other Smooks extensions) for further processing.
- Binding the interchange message data into pre-built Java object models, or custom models if you prefer to use your own.
All the required artifacts for reading any of the UN/EDIFACT directories (and converting to XML) are available in Maven, as are all of the pre-built Java Object models for all the messages defined in all of the UN/EDIFACT directories. To use them, all you need to do is include the appropriate artifacts into your project. See the User Guide.
The new Apache Camel integration allows you to hook Smooks into your Camel routes as a Camel Component or Camel DataFormat. Another important part of the Camel integration are the Smooks extensions that allow you to perform inline routing of Smooks BeanContext data to Camel endpoints i.e. you can also process huge (GB+) data streams.
Putting these two new capabilities together allows us to provide some interesting functionality with respect to Splitting and Routing UN/EDIFACT message Interchanges. We use Smooks to perform the reading, conversion (to XML and/or Java) and splitting of the interchanges and then use Camel to to perform the inline routing of the Java or XML (using the new Camel extensions for Smooks).
We created an example that demonstrates this capability:
- See the Screencast.
- Get the code and try it yourself (the “splitting-camel” example).
At last we’re nearly there with v1.4. As well as 85+ bug fixes, Smooks v1.4 includes the following new highlight features:
- Out of the box support for UN/EDIFACT Interchange message. See Examples.
- Apache Camel Integration. See Examples.
- A Dynamic Model Builder that’s very handy for dealing with complex evolving configuration namespaces on top of a single Java Object Model. Supports model reading and writing. See Examples.
But that’s not all by any means. See here for a full list of Fixes and Features
Back to top