| Summary: | CTFileRecoveryPr Class Missing | ||
|---|---|---|---|
| Product: | POI | Reporter: | vikram <cse.vikram> |
| Component: | XSSF | Assignee: | POI Developers List <dev> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 3.9-FINAL | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Attachments: | Dump of the system crash where no class definition found error is shown | ||
|
Description
vikram
2014-04-02 18:45:46 UTC
This is fully covered in the FAQ - http://poi.apache.org/faq.html#faq-N10025 (Please re-open the bug if you have a unit test to get it pulled into the poi-ooxml schemas automatically) The same piece of code is working on my friend's system with same sets of poi jar. What can be the probable reason of failure on my system. I just do not un-necessarily want to add the ooxml-schema jar as its so huge. Created attachment 31469 [details]
Dump of the system crash where no class definition found error is shown
You still need to read the FAQ, and you still need to do what it suggests... Resolving based on previous comment. Please reopen if you still thing there is a problem in POI after following the steps outlined in the FAQ entry. IS there anything to do with the JDK version difference on two machines. JDK shouldn't make any difference. Make sure you've really included the required jars on the classpath, and followed the instructions in the FAQ. Different machines with different JDKs just means more chances to have different jars... I am sure because I have exported the poi jar from the machine on which the code is working. Also the classpath is correctly configured because I simply delete the poi jar and add ooxml jar at same location in project folder and the behavior (system crash) is replicated, while if i again delete poi jar and add ooxml jar at same location the system runs correctly. Really missing the concept behind this. I still cannot see where there is a problem in POI. Maybe this is some classpath-problem or old jar file loaded from somewhere else, but likely not caused by anything in POI, therefore I am closing this once more as I don't know what else we can possibly provide here. |