Renat Zubairov has been doing some really cool stuff with Smooks UN/EDIFACT. On top of the ECT tooling, he has built tools for generating Eclipse EMF Ecore (XMI) models for each of the EDI Mapping Models being produced by ECT. On the back of this work, he has been able to build an Editor for Eclipse, allowing you to read and write UN/EDIFACT messages from inside Eclipse.
See more here on the Smooks Wiki.
The UN/EDIFACT Editor for Eclipse is cool, but I think the wider impact of these capabilities is even cooler. This is really important work because it will open a number of really important doors in terms of our ability to process and transform not just UN/EDIFACT, but EDI in general (X.12, HL7 etc). Our long-term goal is to add support for X.12, HL7 etc to ECT (i.e. build conversion tools for these standards). Once we do this, we will be able to provide out-of-the-box support for these EDI formats on the Smooks Runtime. We hope it will also mean that we can use this work that Renat is doing to automate building of Ecore/XMI models for these same formats. Once we have these Ecore/XMI models, we hope we will be able to:
This is awesome stuff. Keep up the great work Renat!!!
Here is a quick overview where you can find the slides presented on the Smooks Community Day 2010:
Bård (Langöy) and I have been doing lots of work on improving our EDI support, specifically in the area of handling UN/EDIFACT (WikipediA) message Interchanges. The following improvements are now in the Smooks v1.4 codebase (available from the 1.4-SNAPSHOT):
So that’s what’s available in the current 1.4 codebase (1.4-SNAPSHOT), but we’re also in the process of making more additions to this for Smooks v1.4. We’re extending the EDI Java Compiler (EJC) tools to support Java Model generation from the EDI Mapping Model sets generated by the ECT tool (mentioned above). We’ll also make these available as pre-built jar files from the Maven repository.
Another improvement we’ve made in the 1.4 codebase is the addition of support for Java Model to EDI serialization on the EJC generated Java object models, meaning we’ll be able to do full round trip binding of an EDI (and UN/EDIFACT) message to a populated Java Object model that can be modified and then serialize back out to an EDI stream. Or, your app can “manually” construct the same Java Object models and serialize them out to an EDI Stream (think JAXB).
The easiest way to consume UN/EDIFACT messages using Smooks is to use ECT (EDI Conversion Tool) to generate the EDI Mapping Model set (if we haven’t already pre-built them). The steps are really easy:
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>org.milyn.edi.unedifact</groupId> <artifactId>d03b-mapping</artifactId> <version>1.0.SNAPSHOT</version> <name>UN/EDIFACT - D03B - Mapping Model</name> <build> <plugins> <plugin> <groupId>org.milyn</groupId> <artifactId>maven-ect-plugin</artifactId> <version>1.4-SNAPSHOT</version> <configuration> <src>d03b.zip</src> <srcType>UNEDIFACT</srcType> </configuration> <executions> <execution> <goals><goal>generate</goal> </goals></execution> </executions> </plugin> </plugins> </build> </project>
Of course when we execute this step, we will perform “mvn clean deploy” and install the jar file in the public maven repository, making it publicly available and thereby removing the need for you to perform this step. A peek into the public SNAPSHOT repo shows that we’ve started this process.
Using a generated EDI Mapping Model set jar in your application (via Smooks) is trivial. You need to:
<unedifact:reader mappingModel="urn:org.milyn.edi.unedifact:d03b-mapping:1.0-SNAPSHOT" />
Using the “urn:<groupId>:<artifactId>:<version>” URN pattern, Smooks can find the EDI Mapping Model set jar file on the classpath,
And that’s about it. The associated Smooks instance will accept a UN/EDIFACT message interchange containing one or more messages defined in the d03b.zip definitions directory zip file, and will generate a stream of SAX events into Smooks, which can be processed using all the other Smooks capabilities (Java Binding, Validation, Templating etc). As stated earlier, the improvements we are working on for EJC will result in us being able to generate Java Object models from an EDI Mapping Model set jar.
Check out and build the Smooks examples from https://svn.codehaus.org/milyn/trunk/smooks-examples (mvn install).
Change into the “ect-unedifact” directory after building all the examples (must build them all so as to install the poms) and run the example using mvn exec:java. The ect-unedifact example depends on the “d03b-mapping” module which has been pre-built and is available in the public SNAPSHOT repo.
And guys…. PLEASE let us know how you get on with this stuff… things you like and dislike etc !!!