Denodo Jar get conflicts with Play Framework Jar

Question

I am using : Latest version of play framework wi.-> 2.3.5 Latest version of Denodo -> 5.5 win

Denodo is using Apache Common Codec 1.3 whereas Play is using few new methods introduced in Apacahe Common Codec 1.4 (Eg Caused by: java.lang.NoSuchMethodError: org.apache.commons.codec.digest.DigestUtils.sha1Hex(Ljava/lang/String;)Ljava/lang/String; ). Somehow denodo's legacy jar is getting preference over play's jar.

Is there any way to get rid of this situation?

Answer 1

Instead of using the denodo-vdp-jdbcdriver.jar , use the denodo-vdp-jdbcdriver-basic.jar .

From the Denodo Virtual DataPort Developer Guide:

There are two versions of the JDBC driver to connect to Virtual DataPort (both located in the folder /lib/vdp-jdbcdriver-core/)

1. denodo-vdp-jdbcdriver.jar (recommended version).
2. denodo-vdp-jdbcdriver-basic.jar

Both versions are the same except that the “basic” one does not contain the third-party dependencies required by the driver.