You can translate the question and the replies:

Denodo Jar get conflicts with Play Framework Jar

Hi Group, 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 (E.g. 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. Advance thanks !
user
27-08-2015 09:07:25 -0400
code

1 Answer

Hi, I suppose this issue arises when you try to use Denodo's JDBC driver (denodo-vdp-jdbcdriver.jar) in your Play Framework environment. As you said, that driver includes the Apache Commons Codec library, version 1.3, which conflicts with the one provided by Play. To avoid this, you need to use the "basic" version of the JDBC driver (denodo-vdp-jdbcdriver-basic.jar), which doesn't contain the third-party dependencies required by the driver. Keep in mind that you will need to add to your classpath the Apache libraries the driver needs, including Commons Codec (in your case, version 1.4). Please check the section 2.2 of the Denodo Virtual DataPort Developer Guide (https://community.denodo.com/docs/view/document/Denodo%20Express/Denodo%205.5/Virtual%20DataPort%20Developer%20Guide) for more details on this process. Hope this helps.
Denodo Team
27-08-2015 15:33:09 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here