Comments on: Top 10 SOA Pitfalls: #4 – Incorrectly applied Canonical Data Model http://blog.xebia.com/2008/06/02/top-10-soa-pitfalls-4-incorrectly-applied-canonical-data-model/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: BJ http://blog.xebia.com/2008/06/02/top-10-soa-pitfalls-4-incorrectly-applied-canonical-data-model/#comment-109464 BJ Wed, 14 Sep 2011 18:19:55 +0000 http://blog.xebia.com/?p=575#comment-109464 Some folks I'm working with are pushing to use the CDM objects (jaxb generated I believe) as the entities to persist in our persistance layer. Is this out of scope for CDM? Should we be using seperate entity objects when persisting to the DB? Thanks. Some folks I’m working with are pushing to use the CDM objects (jaxb generated I believe) as the entities to persist in our persistance layer. Is this out of scope for CDM? Should we be using seperate entity objects when persisting to the DB? Thanks.

]]> By: Raju Bodapati http://blog.xebia.com/2008/06/02/top-10-soa-pitfalls-4-incorrectly-applied-canonical-data-model/#comment-93755 Raju Bodapati Wed, 06 Jan 2010 21:50:46 +0000 http://blog.xebia.com/?p=575#comment-93755 Very well said. One good example for industry standard is the ACORD XML (refer www.acord.org.) They defined generic insurance data standards. Entities that are exchanged between two or many systems should be part of CDM. The diagram is a little misleading. Very well said.

One good example for industry standard is the ACORD XML (refer http://www.acord.org.) They defined generic insurance data standards. Entities that are exchanged between two or many systems should be part of CDM. The diagram is a little misleading.

]]>