我正在使用:最新版本的play framework wi .-> 2.3.5 Denodo的最新版本 - > 5.5 win
I am using : Latest version of play framework wi.-> 2.3.5 Latest version of Denodo -> 5.5 win
Denodo正在使用Apache Common Codec 1.3,而Play正在使用Apacahe Common Codec 1.4中引入的一些新方法(例如: java.lang.NoSuchMethodError:org.apachemons.codec.digest.DigestUtils.sha1Hex (Ljava /郎/字符串;)Ljava /郎/字符串; )。不知怎的,denodo的传统jar正在偏爱游戏的jar。
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.apachemons.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?
推荐答案不使用 denodo-vdp-jdbcdriver.jar ,而是使用 denodo-vdp-jdbcdriver-basic.jar 。
来自Denodo虚拟数据开发者指南:
From the Denodo Virtual DataPort Developer Guide:
有两个版本连接到Virtual DataPort的JDBC驱动程序(均位于文件夹/ lib / vdp-jdbcdriver-core /中)
There are two versions of the JDBC driver to connect to Virtual DataPort (both located in the folder /lib/vdp-jdbcdriver-core/)
两个版本都是相同的,只是基本版本不包含驱动程序所需的第三方依赖项。
Both versions are the same except that the "basic" one does not contain the third-party dependencies required by the driver.
更多推荐
Denodo Jar与Play Framework Jar发生冲突
发布评论