Hi, BUGs in Transformers development: - transformer cannot be initiated - missing libraries - java transformer cannot be builded - missing libraries - no transformer can be exported -> ini is obsolete, xml is invalid - in APP10 project is also BUG - using of Java 1.6 is obsolete - must be rewritten to 1.7
Hi, BUGs in Transformers development: - transformer cannot be initiated - missing libraries - java transformer cannot be builded - missing libraries - no transformer can be exported -> ini is obsolete, xml is invalid - in APP10 project is also BUG - using of Java 1.6 is obsolete - must be rewritten to 1.7
I created a new project based on the example and created a XML to JSON transformer in Dev Studio, so far things are working fine and I could get my transformer working in 22R1 😎
jdk version- I used openJDK 17 and it worked without a problem.
ifs-fnd-j2ee.jar contains ifs.fnd.base related sources as well. I will update the documentation accordingly.
/Udesha
Thanks a lot Udesha :)
Hi, with all these libraries is now possible to develop transformer (both types) in 22R1 project using 22.1 DS.
(But still are here issues with wrong *.jar name and generated *.ins and *.xml file)
BR
Hi, with all these libraries is now possible to develop transformer (both types) in 22R1 project using 22.1 DS.
(But still are here issues with wrong *.jar name and generated *.ins and *.xml file)
BR
Hi Filip,
regarding the .jar name problem, what was the real issue there? How did you create your transformer project?
Cheers!
Damith
Hi @dsj, transformer project is generated from Transformer model file via “Horizontal Workflow”. And whole development could be done inside IFS project, there is no need of usage underlaying Maven Transformer project.
(Initialize raising error - Generate Code first despite of it is already done - for XSL close model and reopen it, for Java restart whole IDE, after Code generation helps)
This is only way how to develop transformer for APP10, where is *.INS file needed to install it via delivery. No other way will generate *.xml and *.ins. (these files are generated after test run is successful - do not forget fill Input.xml and Expected.xml - be aware of newlines)
And as I said, it still works APP10 way also for IFS Cloud - same files generated, same jar name → CEcbCurrencyRates-10.0-core.jar.
BR
Hi @dsj, transformer project is generated from Transformer model file via “Horizontal Workflow”. And whole development could be done inside IFS project, there is no need of usage underlaying Maven Transformer project.
(Initialize raising error - Generate Code first despite of it is already done - for XSL close model and reopen it, for Java restart whole IDE, after Code generation helps)
This is only way how to develop transformer for APP10, where is *.INS file needed to install it via delivery. No other way will generate *.xml and *.ins. (these files are generated after test run is successful - do not forget fill Input.xml and Expected.xml - be aware of newlines)
And as I said, it still works APP10 way also for IFS Cloud - same files generated, same jar name → CEcbCurrencyRates-10.0-core.jar.
BR
Hi @InfFilipV,
I doubt we could use transformer model in cloud, but upto RnD to comment on that. As I interpreted, the middle-tier modeling is now deprecated? Please verify that before committing the changes in cbp.
I created my transformer using the example project given in the documentation and could change the .jar name in build.xml