#10 Replace Xerces with JAXP

[Adam Hawkins]

from forum post: https://sourceforge.net/forum/forum.php?thread_id=3034680&forum_id=577988

It would be preferable if the JAXP api could be used for parsing the XMLA responses rather than explicitly using Xerces.

This is currently prohibiting using olap4j's XMLA as a container managed datasource since the Xerces version (and package structure) is conflicting with the parser implementation provided by the container.

e.g. dropping the olap4j.jar & dependent xerces.jar in tomcat/lib and adding the following to the server.xml should make a pooled datasource available via JNDI @ jdbc/miq.olapdb

<Resource auth="Container" <br="">description="Olap database for Reporting"
driverClassName="org.olap4j.driver.xmla.XmlaOlap4jDriver"
maxActive="100" maxIdle="30"
name="jdbc/miq.olapdb"
type="javax.sql.DataSource" url="jdbc:xmla:Server=http://192.168.1.10:8080/mondrian/xmla;Provider=Mondrian;DataSource=olapfabric;Catalog=Mobileiq_olap;"
/>

However this throws a class cast between conflicting xerces versions.

Using JAXP should allow the container (or jdk) to provided the parser implementation itself.