https://answers.axonivy.com/questions/2179/unable-to-use-apache-poi-getting-schematypeloaderexception<p>I'm trying to use Apache POI (3.10 or 3.15) with XpertIvy Designer v5.0.18 and I'm getting the following exception:</p> <pre><code>SchemaTypeLoaderException: XML-BEANS compiled schema: Incompatible minor version - expecting up to 23, got 24 (schemaorg_apache_xmlbeans.system.sE130CAA0A01A7CDE5A2B4FEB8B311707.index) - code 3 java.lang.reflect.InvocationTargetException RuntimeException: Could not instantiate SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the version of xbean.jar correct? </code></pre> <p>I saw a few older threads (<a href="http://answers.axonivy.com/questions/511/poi-conflicted-xmlbeans-jars">POI conflicted xmlbeans.jar</a> [2014] or <a href="http://answers.axonivy.com/questions/1225/what-is-axis-lib-used-for">what is axis lib used for</a> [2015]) regarding this issue.</p> <p>Is it really true that you <strong>still have to hack</strong> the designer plugins folder and some server folder too??? </p>enFri, 18 Nov 2016 15:11:36 -0500https://answers.axonivy.com/questions/2179/unable-to-use-apache-poi-getting-schematypeloaderexception/2200<p>You could try to work around the problem by setting a ThreadContextClassloader in the area where you access POI code. </p> <pre><code>ClassLoader oldTcl = Thread.currentThread().getContextClassLoader(); try { Thread.currentThread().setContextClassLoader(APoiClass.class.getClassLoader()); // ANY POI INVOKER CODE } finally { Thread.currentThread().setContextClassLoader(oldTcl); } </code></pre> <p>Maybe this makes engine and designer hacks obsolete.</p>Reguel WermelingerFri, 18 Nov 2016 15:11:36 -0500https://answers.axonivy.com/questions/2179/unable-to-use-apache-poi-getting-schematypeloaderexception/2200https://answers.axonivy.com/questions/2179/unable-to-use-apache-poi-getting-schematypeloaderexception/2180<p>In short: The hack is no longer required. Since 6.6.1 POI can be used in a project without any library conflicts at runtime.</p> <hr> <p><strong>Axon.ivy 6.6.1 and younger</strong></p> <p>These kinds of JAR hell issues are gone from 6.6.1 upwards. </p> <p>In the <strong>Designer</strong> many libraries were removed from the Axon.ivy Classpath container. Practically this means that <code>Webservice Process (CXF)</code> and <code>Webservice Call (AXIS2)</code> libraries are no longer on the classpath of the project. And as xmlbeans is a dependency of CXF, the conflict with POI is gone. These old libraries can be added to classpath manually in the preferences, if anyone used them to patch AXIS stubs or by accident. <a href="http://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.processmodeling.html#ivy.project.preferences.java">http://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.processmodeling.html#ivy.project.preferences.java</a></p> <p>The <strong>Engine</strong> is now also delivered as OSGI version. This means that the proper ClassLoader isolation per Bundle behaves as it does in the Designer. So a huge runtime behavior difference is gone since 6.6.1. The OSGI Engine will become the default version of the Engine. We do not plan to support the OS specific packages any longer due its classloading shortcomings. But for a short time we still release the alternative packages that can be used if you face migration issues.</p> <hr> <p><strong>Axon.ivy 6.5.0 and older</strong></p> <p>The ugly workaround is still required. </p> <ul> <li>Designer: manually patch the JAR in the plugins directory. </li> <li>Engine: rename the /lib/shared/xmlbeans_2.4.0.jar to somethink like xmlbeans_2.4.0.jar.deactivated</li> </ul>Reguel WermelingerMon, 14 Nov 2016 08:52:28 -0500https://answers.axonivy.com/questions/2179/unable-to-use-apache-poi-getting-schematypeloaderexception/2180