on 06-26-2008 11:13 AM
Hi,
What's the most efficient method: SAX, DOM or JAXB?
Hi Indrajit,
SAP recommends the graphical mapping, but all times graphical may not
suitable to our requirements,
so based on our requirement we select the mapping type.
Graphical mapping is the simplest of all mappings and easy and we have
a mapping editor and standard
functions available. when this becomes too complex, or this functions
are not enough then we generally
opt for java or xslt or ABAP mappings,
In general ABAP mapping preference is very less.
If we need many functions then we will go for XSLT mapping. If there
are some predefined functions
in the java to suitable to our requirement then we will go for the Java
mapping.
If data is less then
Graphical mapping -
> Java(sax parser)mapping -
> Java(dom
parser)mapping -
>
XSLT mapping -
> ABAP mapping.
If data is high then
XSLT mapping -
> Java(sax parser)mapping -
> Graphical
mapping(internally it uses SAX)
-
> Java(dom parser)mapping -
> ABAP mapping.
Features of different mappings are as follows
Message Mapping
1) Graphical design and tset environment
2) Queue based model allows handling of very large documents
3) Extensible via Java user defined Functions
XSLT Mapping
1)Open Standard
2)Portable
3) Extensible via Java user defined functions
4)Memory overhead for very large documents
Java Mapping
1)Flexiblity of Java programing language
2) java mapping program is responsible for parsing/rendering XML
ABAP
1)Leverage existing ABAP base
2) ABAP mapping program is responsible for parsing/rendering XML
JAVA MAPPING:
A java map written by a highly experienced java programmer will be the best mapping performance wise.
Message or graphical maps are also good performance wise but they are used more because of ease of use and the ability to view context/queues thus making debugging easier. Internally a message map is a java code.
Java Mapping comes up with SAX parser and DOM Parser.
Java Mapping with SAX parser is performance wise better and even Graphical mapping also follows the SAX parser internally.
Then you can prioritize the DOM parser.
Mapping Performences Blog:
Check this blog
/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs
For performance analysis
Performance Tuning Checks in SAP Exchange Infrastructure: /people/prasad.illapani/blog/2007/03/08/performance-tuning-checks-in-sap-exchange-infrastructure
Performance Tuning Checks in SAP Exchange Infrastructure(XI): Part-II: /people/prasad.illapani/blog/2007/04/20/performance-tuning-checks-in-sap-exchange-infrastructurexi-part-ii
SAP NetWeaver XI Performance Analysis - Webinar Powerpoint
SAP Exchange Infrastructure-- Tuning Guide
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please refer http://www.codeproject.com/KB/XML/java_xml-binding_objects.aspx.
Don't post same questions in multiple threads. Also Pl,ease mark one of them answered.
Regards
Aashish Sinha
PS : reward points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.