I 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
description="Olap database for Reporting"
However this throws a class cast between conflicting xerces versions.
Using JAXP should allow the container (or jdk) to provided the parser implementation itself.
Sounds like a good idea. Can you log an RFE for this?
Log in to post a comment.