Re: POI xlsx indeterminism

One simple approach could use the text extraction functionality of POI and only compare the extracted text of the two workbooks, maybe that already provides the wanted "is equal" functionality? Dominik On Aug 1, 2016 6:35 PM, "Javen O'Neal" wrote: Within your

Re: POI xlsx indeterminism

Within your !hash1.equals(hash2) code, you could save the byte streams to disk, extract the zip files, and use a diff utility to figure out why they're different. We use a lot of hash maps, which have nondeterministic order. If those maps are serialized out as , then attrs could be swapped. Some

Re: POI xlsx indeterminism

On Mon, 1 Aug 2016, armin.winte...@ldbv.bayern.de wrote: we've been experiencing an indeterminism problem with POI's xlsx format, when generating hash values with the following method in testng test cases: XLSX uses Zip files, which contain within them file dates. If you're comparing the

Re: POI xlsx indeterminism

-- View this message in context: http://apache-poi.1045710.n5.nabble.com/POI-xlsx-indeterminism-tp5724269p5724270.html Sent from the POI - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@poi.

POI xlsx indeterminism

Dear POI dev team, we've been experiencing an indeterminism problem with POI's xlsx format, when generating hash values with the following method in testng test cases: FileTest: @Test(enabled = true) // indeterminism at random iterations, such as 400 or 1290 public void emptyXLSXTest()