Upgrade Apache POI in MI

[SanojPunchihewa]

Description

In MI 4.x.x versions we are using Apache POI 3.x.x version which is outdated it's preferred to migrate to 5.x.x version. Since this is a major version change, there will be architectural changes and it's better to evaluate the feasibility and backward compatibility beforehand.

Affected Component

MI

Version

No response

Related Issues

No response

Suggested Labels

No response

[lasanthaS]

Hi all,

I upgraded the Apache POI to its latest version i.e. 5.2.3 but encountered a few compilation issues due to API changes. I am currently looking into those issues. I will update the ticket once the issues are resolved.

Regards,
Lasantha

[lasanthaS]

Hi all,

I could resolve the above compilation issues due to the API changes. However, I encountered a class loading issue in the poi-ooxml jar while deploying a data service. I am currently looking into that issue.

Regards,
Lasantha

[lasanthaS]

Hi all,

We were able to resolve the above class loading issue by packing some missing resource files in poi orbit JARs. However, we are still facing a few more issues and currently looking into those.

[lasanthaS]

Hi all,

I was able to sort the above class loading issue by restructuring OSGi imports/exports. And now the functionality is working fine. But while running tests on the micro-integrator repo, there is a test failure due to a connection refused error as the particular test server is not spawning up correctly. But once a separate MI server is deployed with those test artifacts and pointing the tests to that particular server works as expected. I am working on debugging those respective test cases to isolate the issue right now.

Thanks,
Lasantha

[lasanthaS]

Hi all,

I tried updating the Apache POI version to its latest i.e. 5.2.3, however, encountered some test failures due to conflicting org.apache.xmlbeans versions in the POI dependency and the pack. It seems to be a major change from the product perspective to fix this issue, therefore holding this for a moment and will get back to it later.

Regards,
Lasantha