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) |
Rene spronk (talk | contribs) |
||
| Line 3: | Line 3: | ||
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. | ||
| − | [[Image:Enovationmatrix. | + | [[Image:Enovationmatrix.jpg]] |
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. | 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. | ||
Latest revision as of 16:25, 24 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.
