This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA: E-Novation"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (New page: The E-Novation approach involves the AR-AO-MO-MS squares. AO to AR uses Hibernate; AO to/fro MO is custom Java code; MO-MS is based on JAXB. Image:Enovationmatrix.gif Given that the ...) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | [[category:RIMBAA]] ''This page uses terminology as defined in [http://www.ringholm.de/docs/03100_en.htm this whitepaper].'' | ||
| + | |||
The E-Novation approach involves the AR-AO-MO-MS squares. AO to AR uses Hibernate; AO to/fro MO is custom Java code; MO-MS is based on JAXB. | The E-Novation approach involves the AR-AO-MO-MS squares. AO to AR uses Hibernate; AO to/fro MO is custom Java code; MO-MS is based on JAXB. | ||
Revision as of 17:25, 23 July 2008
This page uses terminology as defined in this whitepaper.
The E-Novation approach involves the AR-AO-MO-MS squares. AO to AR uses Hibernate; AO to/fro MO is custom Java code; MO-MS is based on JAXB.
Given that the application object model (AO) is loosely based on a couple of R-MIMs - and optimized for use with the Hibernate tool one could argue that in fact this implementation involves the RR-RO-MO-MS squares.
