topic tFileOutputMSXML build issue in talend 7.3.1 in Talend Studio

tFileOutputMSXML build issue in talend 7.3.1

JElis1633359493 — Mon, 04 Oct 2021 15:07:15 GMT

Hi,

We work with Talend Open Studio for Data Integration 7.3.1.

One of our job uses the standard component tFileOutputMSXML.

When defining a loop element, the job doesn't compile and there is the following error :

The method add(int, Element) in the type List<Element> is not applicable for the arguments (int, Branch)

The code is :

((org.dom4j.Element) (nameToElement_tFileOutputMSXML_1.get("subTreeRootParent")))

.elements()

.add(order_tFileOutputMSXML_1, nameToElement_tFileOutputMSXML_1.get("loop"));

Is this component work in 7.3.1 with a loop element ?

How can i fix this issue without changing the talend open studio version (the 7.4.1 and the 8.0.1 are not released) ?

Re: tFileOutputMSXML build issue in talend 7.3.1

Anonymous — Mon, 11 Oct 2021 06:40:47 GMT

Hello,

How did you define a loop element in tfileoutputMSXML?

We will appreciate it a lot if you could post your tfileoutputMSXML component setting screenshots on community.

Best regards

Sabrina

Re: tFileOutputMSXML build issue in talend 7.3.1

JElis1633359493 — Mon, 11 Oct 2021 06:58:41 GMT

Hi,

Here is the screenshots.

The component

Inside it

Re: tFileOutputMSXML build issue in talend 7.3.1

JElis1633359493 — Wed, 20 Oct 2021 13:01:19 GMT

Hi,

Nobody uses this component in 7.3.1 ?

Re: tFileOutputMSXML build issue in talend 7.3.1

Anonymous — Thu, 21 Oct 2021 03:12:01 GMT

Hello,

There can be only one loop element in xml component. But you can set group element.

I guess you didn't set the component correctly as we cannot repro this issue on V 7.3.1. Is there any detailed steps to reproduce your issue? If so, we will appreciate it if you could post here.

Best regards

Sabrina

Re: tFileOutputMSXML build issue in talend 7.3.1

philorg — Thu, 03 Nov 2022 16:42:39 GMT

You can modify the file C:\TALEND\TOS_DI-Win32-20200219_1130-V7.3.1\plugins\org.talend.designer.components.localprovider_7.3.1.20200213_1003\components\tFileOutputMSXML\tFileOutputMSXML_begin.inc.javajet to fix this bug.

Line 412 :

<%touchXMLNode.getXMLElement(parentName);%>.elements().add(order_<%=cid%>,<%touchXMLNode.getXMLNode(currEleName);%>);

<%touchXMLNode.getXMLElement(parentName);%>.elements().add(order_<%=cid%>,(org.dom4j.Element)<%touchXMLNode.getXMLNode(currEleName);%>);

Close and reopen TOS 7.3 (or ctrl+shift+F3)