Scribd
Upload
103 views1 page

XSLT Mapping Vs Business Object Mapping

This document compares XSLT mapping and business object mapping for integration flows. It recommends using business object mapping if using Java APIs, custom Java code, custom mediations, or existing business object maps. It recommends using XSLT mapping for simple flows involving web services, filtering, routing, and custom XSL, as XSLT mapping allows reusing XSL and has better array mapping capabilities.

Uploaded by

kumar kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
103 views1 page

XSLT Mapping Vs Business Object Mapping

This document compares XSLT mapping and business object mapping for integration flows. It recommends using business object mapping if using Java APIs, custom Java code, custom mediations, or existing business object maps. It recommends using XSLT mapping for simple flows involving web services, filtering, routing, and custom XSL, as XSLT mapping allows reusing XSL and has better array mapping capabilities.

Uploaded by

kumar kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

XSLT Mapping Vs Business Object Mapping

Reasons to use BO map:

If using SDO Java API / lots of custom Java / custom mediations

If already using BO map in a flow / submaps, then use more BO maps

If mapping to/from Adapters

Reasons to use XSL map:

Particulary good for simple flows, e.g. web service call, filter/route on a header, XSL,
web service call

Can reuse XSL / use custom XSL

Better array mapping capabilities

You might also like