Not logged in | Login
This research initiative was kicked off by Frank Kieviet.
The "non-classic" side of CAPS 6.x does not currently have a message mapping facility that is the equivalent of the classic CAPS JCE (Java Collaboration Editor). This research project explores how we can provide a low-cost addition to the non-classic side that does not rely on proprietary representation formats or tools (JCDs, OTDs), and does not preclude direct manipulation of DOM trees.
For more detailed scoping, look here.
The Test-Driven Message Transformation project is currently in a research state. It is in flux, and may change over time as we evolve better understanding of how to get the optimal user experience for the expected scenarios.
The sources will be distributed as open source using Mercurial as the source control system. The 0.1 version of the source has not been distributed yet, pending a more complete code base.
The documentation will be provided on the wiki.open-esb.java.net website.
(Last meeting: 2008-09-23)
A step-by-step introduction is available here.
You can download the TeDMeT prototype here.
We're working on future developments. See more here.
We analyzed a series of customer projects to extract a profile of real-life business case feature usage. This gives us an idea of the types of structures and mapping that the user can expect in practice, and for which our approach would need to provide a better solution, or at least not prove an impediment.
Some cases could not be processed because they required the extra installation of too many extra products or external facilities to be feasible within the time scope, or proved to be outside the scope of our goal, but we did manage to find and analyze a sufficient large (in our humble opinion) number of cases to give some depth to the conclusions.
A caveat with this study is that we cannot say whether a potential feature was not used because: (a) the user saw no business use-case for it, or (b) the user would have liked to use it be could not because it was absent or too hard to use in the current CAPS release.
Some features that we feel may have merit in the mapper (maybe not V1 but in the future)
We looked at customer projects on the 513 repository on the link provided by Frank and we also imported some of the customer projects provided by Frank. Among the customers were Alliantz, BCBSNC, Lockheed, Nike, BDP, BMW, Borders, GM, Hertz, INS, JCD2JCD, Kroger, Pfizer, prjEmailJCD, Travelers, imLink2212. Some of the customers did not use JCEs, others used small JCEs that did only very standard mappings, and others did complex mappings. From our analysis, we have seen the following:
|4||23-Sep-08 17:54 PM, -0700||Michael J.D. Libourel||7558||to previous|
|3||23-Sep-08 17:14 PM, -0700||Michael J.D. Libourel||7612||to previous | to last|
|2||19-Sep-08 14:35 PM, -0700||Michael J.D. Libourel||8586||to previous | to last|
|1||19-Sep-08 14:17 PM, -0700||Michael J.D. Libourel||8499||to last|