Thank you for this information.
I am currently running a Proof of Concept using the evaluation version of Word Java version 126.96.36.199…
My technical team has found two bugs that would impact our solution, so before we buy, we need to understand if this a known evaluation bugs or the fix situation.
The bugs are bellow.
Looking forward to hearing from you.
Solution Architect - Customer
>>> SIMON BRAINES 24/09/08 12:30 pm >>>
I’ve encountered 2 problems with the Aspose Words API.
- Document fails to save
This occurs after opening a word doc in Aspose, manipulating the object tree and then saving to a different filename. The stack trace is shown below:
[24/09/08 12:06:52:351 EST] 0000002d SystemOut O 2008-09-24 12:06:52,351 ERROR [A.ApplicationExceptionReporter] java.lang.NullPointerException Error attempting to replace tokens in Word file: NOR Plan Stamp Dual Occupancy Unsubdivided Vert.dot java.lang.NullPointerException java.lang.NullPointerException at com.aspose.words.cq.visitParagraphEnd(Unknown Source) at com.aspose.words.Paragraph.accept(Unknown Source) at com.aspose.words.cq.b(Unknown Source) at com.aspose.words.cq.a(Unknown Source) at com.aspose.words.Document.save(Unknown Source) at com.aspose.words.Document.save(Unknown Source) at au.com.swc.common.worddocument.token.TokenReplacer.replace(TokenReplacer.java:112)
This error always occurs when running in non-debug mode (in Eclipse). However, if I run in debug mode then the file saves successfully the first few times but then starts producing corrupt files that Word cannot read. I’ve attached corrupt and valid versions of this file to compare - there appears to be 3 bytes in the header that are different between the 2 files.
- Document fails to open
This problem used to occur using every time a file with more that 1000 characters was opened when using the 1.4 JDK version of Aspose Words (in non-debug mode). I never saw this error when running in debug mode though.
Since moving to the 1.5 JDK version, the problem only occurs in non-debug mode after the “document fails to save” error occurs. It then occurs for every file opened, regardless of size.
The stack trace is:
[24/09/08 12:08:31:245 EST] 0000002e SystemOut O 2008-09-24 12:08:31,245 ERROR [A.ApplicationExceptionReporter] java.lang.NullPointerException The document appears to be corrupted and cannot be loaded. java.lang.NullPointerException java.lang.NullPointerException at com.aspose.words.Paragraph.fY(Unknown Source) at com.aspose.words.g.a(Unknown Source) at com.aspose.words.eu.gc(Unknown Source) at com.aspose.words.dj.parse(Unknown Source) at com.aspose.words.bn.read(Unknown Source) at com.aspose.words.Document.a(Unknown Source) at com.aspose.words.Document.a(Unknown Source) at com.aspose.words.Document.(Unknown Source) at com.aspose.words.Document.(Unknown Source) at au.com.swc.common.worddocument.token.TokenReplacer.replace(TokenReplacer.java:97)
Could you check with Aspose if this is a known issue with the evaluation API? If not, it’s likely that the way I’m manipulating the object tree via the API when replacing token is triggering these issues. However, I’d expect these problems to be consistent instead of producing different results over time.
This message was posted using Email2Forum by sheliah.