View source for MapToEntityWrapper and MapFromEntityWrapper design pattern for integration data mapping.

MapToEntityWrapper and MapFromEntityWrapper design pattern for integration data mapping. / ← Design pattern for integration data mapping

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

== Advantages of using this pattern == * You do not have to create extension points for each mapping class explicitly, as this pattern helps call them dynamically if available. If not, the default baseclass stub extension points are used. The implementation layer can create them on demand instead of a built-on application creating the extension rules unnecessarily. * Every class has the MapTo/FromEntity, which makes it easy to recognize mapping data transforms. '''Note:''' If multiple input channels exist with different input formats, you can append _XML or _JSON or _EDI to clearly distinguish between channel and format mapping rules.

Return to Design pattern for integration data mapping.