how to copy data from one xml files in to another using java xslt

Question

I need to replace all ? in file1.xml with element value present in File2.xml.
And also need to remove extra element node present in File1.xml whose value is not present in File2.xml. (i.e. In my sample input need to remove totalDueWithoutTax element from file1.xml as it is not present in File2.xml.
There may be the cases where we have multiple elements in File2 but only one corresponsing element in File1. Like in my below example we have two salesInfo element in File2 but in File1 we have only one. In that case as a expected output we need both salesInfo element of File2.
This is just sample input. In real scenario input xmls can be different means we can get different format of xmls everytime.

Please suggest me how to do that in java. It would be better if we can achieve this using xslt.

        **File 1 -- input xml**
       <order>
            <orderId>?</orderId>
             <sales>
              <salesInfo>
                <salesChannel>?</salesChannel>
                <senderSystemId>?</senderSystemId>
                <applicationId>?</applicationId>
                <totalDueWithoutTax>?</totalDueWithoutTax>
              </salesInfo>
              <salesid>?</salesid>
           </sales>
        </order>
        
        **File 2 -- input xml**
    
        <order>
          <orderId>4567</orderId>
          <sales>
              <salesInfo>
                <salesChannel>abc</salesChannel>
                <senderSystemId>def</senderSystemId>
                <applicationId>123</applicationId>
                <esignatureCaptureMode>INLINE</esignatureCaptureMode>
              </salesInfo>
              <salesInfo>
                <salesChannel>xyz</salesChannel>
                <senderSystemId>uvw</senderSystemId>
                <applicationId>234</applicationId>
                <esignatureCaptureMode>outline</esignatureCaptureMode>
              </salesInfo>
              <salesid>789</salesid>
        </sales>
        </order>
        
        **Expected output:**
        
        <order>
            <orderId>4567</orderId>
            <sales>
              <salesInfo>
                <salesChannel>abc</salesChannel>
                <senderSystemId>def</senderSystemId>
                <applicationId>123</applicationId>
              </salesInfo>
              <salesInfo>
               <salesChannel>xyz</salesChannel>
                <senderSystemId>uvw</senderSystemId>
                <applicationId>234</applicationId>
              </salesInfo>
              <salesid>789</salesid>
          </sales>
        </order>

All the input comes from file2 and even the tag names are the same. What do you need file1 for? — f1sh
– f1sh, Commented Feb 7, 2022 at 9:47
Will the structure of the two documents always be as shown (i.e. order root element in the first document, root root element) in the second, and you know an order root element in the first document is matched against that root root element in the second document? — Martin Honnen
– Martin Honnen, Commented Feb 7, 2022 at 9:48
@f1sh these are not exactly same. file1 have totalDueWithoutTax element and file 2 have esignatureCaptureMode element. In my expected output i don't want these element. — ankush garg
– ankush garg, Commented Feb 7, 2022 at 9:50
@MartinHonnen i have edited my question. Root element will always be order in both file1 and file2 — ankush garg
– ankush garg, Commented Feb 7, 2022 at 9:53

Michael Kay · Accepted Answer · 2022-02-07 11:46:16Z

2

An "out of the box" suggestion: you might like to think of your file1 as representing a little templating language. If you think of it that way, then one option that comes to mind is to translate your little templating language into XSLT (a translation which, of course, can be done using XSLT).

So your transformation would convert

<salesChannel>?</salesChannel>

to

<salesChannel>
      <xsl:value-of select="order/salesinfo/saleschannel"/>
</salesChannel>

where the expression in the select attribute is obtained by calling path().

The advantage of this approach is that you can start to grow your "little templating language" to include extra features, such as loops and conditionals, as the requirements appear.

answered Feb 7, 2022 at 11:46

Michael Kay

165k11 gold badges97 silver badges173 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Martin Honnen · Accepted Answer · 2022-02-07 11:04:08Z

0

You could consider a group/merge problem:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  version="3.0"
  xmlns:xs="http://www.w3.org/2001/XMLSchema"
  exclude-result-prefixes="#all"
  xmlns:mf="http://example.com/mf"
  expand-text="yes">
  
  <xsl:param name="doc2" select="doc('file2.xml')"/>>

  <xsl:output method="xml" indent="yes"/>
  
  <xsl:function name="mf:merge" as="node()*">
    <xsl:param name="nodes1" as="node()*"/>
    <xsl:param name="nodes2" as="node()*"/>
    <xsl:for-each-group select="$nodes1, $nodes2" group-by="node-name()">
      <xsl:choose>
        <xsl:when test="not(*) and . = '?' and current-group()[2]">
          <xsl:apply-templates select="current-group()[2]"/>
        </xsl:when>
        <xsl:when test="current-group()[1][*] and current-group()[2][*]">
          <xsl:copy>
            <xsl:sequence select="mf:merge(*, current-group()[2]/*)"/>
          </xsl:copy>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each-group>
  </xsl:function>
  
  <xsl:template match="/*">
    <xsl:copy>
      <xsl:sequence select="mf:merge(*, $doc2/*/*)"/>
    </xsl:copy>
  </xsl:template>
    
  <xsl:mode on-no-match="shallow-copy"/>

</xsl:stylesheet>

Depending on the structure or the merging requirements using xsl:for-each-group select="$nodes1, $nodes2" group-by="path(.)" instead of <xsl:for-each-group select="$nodes1, $nodes2" group-by="node-name()"> might be more suitable, for instance if an element can have several child elements of the same name.

edited Feb 7, 2022 at 11:04

answered Feb 7, 2022 at 10:06

Martin Honnen

169k6 gold badges100 silver badges122 bronze badges

4 Comments

ankush garg Over a year ago

Thank you very much for the reply. It is failing in one scenario. If we have multiple <salesInfo> nodes in File2, but File1 have only one <salesInfo> node. In my expected output ... i want all <salesInfo> nodes from File2 but attributes should be common only. Please help me on that.

Martin Honnen Over a year ago

@ankushgarg, consider to edit your question and show samples for that more complicated setting with multiple salesInfo elements in file 2 but only one in file 1, together with the exact output you want for that sample case.

ankush garg Over a year ago

I have edited the question. For better clarity i have put the <salesInfo> element under <sales>. Please refer to my point number 3.

Martin Honnen Over a year ago

@ankushgarg, I have read through your edit but with the new requirement a merging/grouping based on node name or exact XPath, as my two suggestions attempted, can't work as the several elements in the second document have no counterpart for the grouping with the items from the first document. So I am afraid there is no easy adaption of the given answer to the new requirement. I will leave the answer as it is, perhaps it can serve you as an idea how to work out something on your own with XSLT for your more complicated requirements.

Collectives™ on Stack Overflow

how to copy data from one xml files in to another using java xslt

2 Answers 2

Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related