Bug 58762

Summary: Got No Such Method Error Upgrading from 3.9 To 3.11 .IBM Jdk 1.6_26
Product: POI Reporter: RatiKanata Pal <pal.ratikanta>
Component: SXSSFAssignee: POI Developers List <dev>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: P2    
Version: 3.11-FINAL   
Target Milestone: ---   
Hardware: PC   
OS: All   

Description RatiKanata Pal 2015-12-23 05:09:39 UTC
Hi,
We have just upgraded poi 3.9 to 3.11 .And got 

java.lang.NoSuchMethodError:
javax/xml/stream/XMLEventFactory.newFactory()Ljavax/xml/stream/XMLEventFactory

java version : Ibm  Jdk 1.6_26.

Could you please provide any resolution for this.
Comment 1 Javen O'Neal 2015-12-23 07:10:41 UTC
Could you please provide a short, self-contained, correct example and the resulting stack trace that occurs in POI 3.11?
Comment 2 Javen O'Neal 2015-12-23 07:13:44 UTC
Please also attach any resources needed by the example (such as xlsx files) to the bug.

Does this problem occur if you upgrade to POI 3.10 or POI 3.13?
Comment 3 Dominik Stadler 2015-12-23 07:59:16 UTC
Please read the FAQ at http://poi.apache.org/faq.html#faq-N1017E

The relevant snippet for you is likely "IBM Java 6 does not provide all the interfaces required by the XML standards, only IBM Java 7 seems to provide the correct interfaces, so try upgrading your JDK. ", 

POI started to use default XML Parser functionality which is defined as part of the Java VM, but IBM JDK 6 does not provide those, only upgrading to newer IBM JDK seems to fix this...
Comment 4 Nick Burch 2015-12-23 14:38:57 UTC
3.11 is a little old - can you try upgrading to 3.13? (IIRC we added a workaround for broken JVMs at some point)
Comment 5 RatiKanata Pal 2015-12-24 07:33:55 UTC
HI,
Thank you for your quick response . sure we will try with 1.7 once and confirm back.
Thanx rati.
Comment 6 Javen O'Neal 2016-01-31 08:33:43 UTC
Any news on IBM Java 7 (or Oracle Java 6 or OpenJDK 6)?
Comment 7 Dominik Stadler 2016-07-26 20:39:12 UTC
No update for quite some time, therefore closing this as WORKSFORME for now, please reopen with more information if this is still a problem for you.