Summary: | 3.11 new call to XMLEventFactory.newFactory() introduces incompatibility with IBM WAS 7 (IBM 1.6 JDK) | ||
---|---|---|---|
Product: | POI | Reporter: | David <mediocaballero.spam> |
Component: | POI Overall | Assignee: | POI Developers List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 3.11-FINAL | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
David
2015-02-23 12:12:03 UTC
Do all unit tests still pass on an Orcale JVM after the change? (We don't want to make the change and break things on other JVMs!) I haven't been able to test it, but according to API spec, it shouldn't have any effect. newInstance existed since first version of stax api, while newFactoy was introduced in Oracle 1.6.0.18 'to mantain api consistency', but both have the same functionality. http://docs.oracle.com/javase/6/docs/api/javax/xml/stream/XMLEventFactory.html#newInstance(java.lang.String, java.lang.ClassLoader) http://upstream.rosalinux.ru/java/compat_reports/jdk/1.6.0.17_to_1.6.0.18/bin_compat_report.html#Added Also as a reference, other users with the same issue: http://mail-archives.apache.org/mod_mbox/poi-dev/201501.mbox/%3CFB8F943CCE197F4A8C65545509CA885B0180A24F7FD8@MSGRTPCCRF2WIN.DMN1.FMR.COM%3E |