【问题标题】:Play 2.5.3/Ebean: NoSuchMethodError: com.avaje.ebean.config.ServerConfig.getConstraintNaming()播放 2.5.3/Ebean: NoSuchMethodError: com.avaje.ebean.config.ServerConfig.getConstraintNaming()
【发布时间】:2016-06-16 00:24:12
【问题描述】:

我正在使用 Play 2.5.3 框架,无论出于何种原因,Ebean 在为我的本地(内存中)数据库创建进化时似乎都失败了。这是完整的堆栈跟踪。

[info] play.api.UnexpectedException: Unexpected exception[NoSuchMethodError: com.avaje.ebean.config.ServerConfig.getConstraintNaming()Lcom/avaje/ebean/config/DbConstraintNaming;]
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1$$anonfun$apply$1$$anonfun$1.apply(DevServerStart.scala:174)
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1$$anonfun$apply$1$$anonfun$1.apply(DevServerStart.scala:126)
[info]  at scala.Option.map(Option.scala:146)
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1$$anonfun$apply$1.apply(DevServerStart.scala:126)
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1$$anonfun$apply$1.apply(DevServerStart.scala:124)
[info]  at scala.util.Success.flatMap(Try.scala:231)
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1.apply(DevServerStart.scala:124)
[info]  at play.core.server.DevServerStart$$anonfun$mainDev$1$$anon$1$$anonfun$get$1.apply(DevServerStart.scala:116)
[info]  at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
[info]  at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
[info] Caused by: java.lang.NoSuchMethodError: com.avaje.ebean.config.ServerConfig.getConstraintNaming()Lcom/avaje/ebean/config/DbConstraintNaming;
[info]  at com.avaje.ebean.dbmigration.model.CurrentModel.<init>(CurrentModel.java:37)
[info]  at play.db.ebean.EbeanDynamicEvolutions.generateEvolutionScript(EbeanDynamicEvolutions.java:91)
[info]  at play.db.ebean.EbeanDynamicEvolutions.lambda$create$4(EbeanDynamicEvolutions.java:59)
[info]  at play.db.ebean.EbeanDynamicEvolutions$$Lambda$33/1642038057.accept(Unknown Source)
[info]  at java.util.HashMap.forEach(HashMap.java:1280)
[info]  at play.db.ebean.EbeanDynamicEvolutions.create(EbeanDynamicEvolutions.java:58)
[info]  at play.api.db.evolutions.ApplicationEvolutions.start(ApplicationEvolutions.scala:40)
[info]  at play.api.db.evolutions.ApplicationEvolutions.<init>(ApplicationEvolutions.scala:150)
[info]  at play.api.db.evolutions.ApplicationEvolutionsProvider.get$lzycompute(EvolutionsModule.scala:53)
[info]  at play.api.db.evolutions.ApplicationEvolutionsProvider.get(EvolutionsModule.scala:53)

谷歌搜索这个异常让我几乎没有任何信息。

在我的“application.conf”文件中,

ebean.default = ["models.*"]

    db {
      # You can declare as many datasources as you want.
      # By convention, the default datasource is named `default`

      # https://www.playframework.com/documentation/latest/Developing-with-the-H2-Database
      default.driver = org.h2.Driver
      default.url = "jdbc:h2:mem:play"
      default.username = sa
      default.password = ""

      # You can turn on SQL logging for any datasource
      # https://www.playframework.com/documentation/latest/Highlights25#Logging-SQL-statements
      #default.logSql=true
    }

这似乎是其他人使用的。我认为也可能是问题的 ebean.properties 文件仅包含

ebean.namingconvention=com.avaje.ebean.config.MatchingNamingConvention

我的 build.sbt 文件如下所示:

name := """Project-CS2340"""

version := "1.0-SNAPSHOT"

lazy val root = (project in file(".")).enablePlugins(PlayJava, PlayEbean)

resolvers ++= Seq(
  "webjars"    at "http://webjars.github.com/m2"
)

scalaVersion := "2.11.7"

libraryDependencies ++= Seq(
  javaJdbc,
  cache,
  javaWs,
  "org.webjars"               %% "webjars-play"       % "2.3.0",
  "org.webjars"               % "bootstrap"           % "3.0.0" exclude("org.webjars", "jquery"),
  "org.webjars"               % "jquery"              % "1.8.3",
  "org.avaje.ebeanorm" % "avaje-ebeanorm" % "4.6.2"
)

playEbeanDebugLevel := 4

fork in run := true

今天早些时候,该应用程序正常运行,我想我更改了一些内容并在休息时忘记了它。老实说,不知道。

【问题讨论】:

    标签: java playframework ebean nosuchmethoderror


    【解决方案1】:

    在你的 build.sbt 文件中替换 ebean 的库依赖

    "org.avaje.ebeanorm" % "avaje-ebeanorm" % "4.6.2"
    

    以下

    "org.avaje" % "ebean" % "2.7.3"
    

    祝你好运

    【讨论】:

    • 嘿,很遗憾,这不起作用。我更改了该行并将下载的新 .jar 添加到我的项目的 lib 文件夹中。还有其他想法吗?感谢您的初步帮助!
    • 我又弄乱了我的依赖项并让它工作。将多个版本的 ebean 作为依赖项似乎存在一些问题。摆脱除 ebean-2.7.3 和 avaje-ebeanorm-6.18.1 之外的所有这些,并对我的 build.sbt 文件进行上述更改解决了问题。
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2013-02-27
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2013-09-25
    • 1970-01-01
    相关资源
    最近更新 更多