We have two entries in the FAQ [1] about file validation, which I haven't used myself yet ... and probably are futile in your case. You can try to validate against the ECMA 376 schemes.
If I have similar problems I try to go step-wise from the simple case to the complex ... and yes, it's sometimes quite time consuming. Can you try your shaded jar in the unit test? ... my guess is, it might not include all XmlBeans files (*.xsb) [1] https://poi.apache.org/help/faq.html On 03.02.20 21:25, Kuro Kurosaka wrote: > The .xlsx file from the test run has the same file structure as the .xlsx > from the real run that doesn't open. > The JAR I upload to an application server is shaded and includes the POI > library that is relocated to its version > specific packages to avoid collision. So it's the same version of POI as > the test run. > > If there is no better way, I could somehow record all POI calls in the real > run, and ptu it to the unit test, > but I'd rather want to avoid this route as it is very time consuming. I am > hoping there's a way for > Excel to tell me what errors it is seeing.
signature.asc
Description: OpenPGP digital signature
