【问题标题】:JPA still have a reference of a deleted Entity, hence generating ExceptionJPA 仍然有一个已删除实体的引用,因此会生成异常
【发布时间】:2023-03-18 13:40:01
【问题描述】:

我删除实体FriendWith 并创建RelationShip。但是 JPA 仍然认为FriendWith 在那里。当我在这里部署 EE 应用程序时,这是我在服务器日志中得到的。

[#|2010-11-05T14:31:51.190-0400|INFO|glassfish3.1|javax.enterprise.system.core.classloading.com.sun.enterprise.loader|_ThreadID=17;_ThreadName=Thread-1;|com.scholar.entity.<error> actually got transformed|#]

我知道com.scholar.entity.&lt;error&gt;参考com.scholar.entity.FriendWith

java.lang.ExceptionInInitializerError
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(Class.java:247)
  at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getClassForName(PrivilegedAccessHelper.java:88)
  at org.eclipse.persistence.descriptors.ClassDescriptor.convertClassNamesToClasses(ClassDescriptor.java:1230)
  at org.eclipse.persistence.sessions.Project.convertClassNamesToClasses(Project.java:362)
  at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:332)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:157)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:214)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:202)
  at org.glassfish.persistence.jpa.PersistenceUnitLoader.doJava2DB(PersistenceUnitLoader.java:371)
  at org.glassfish.persistence.jpa.JPADeployer$2.visitPUD(JPADeployer.java:241)
  at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:279)
  at org.glassfish.persistence.jpa.JPADeployer.iterateInitializedPUsAtApplicationPrepare(JPADeployer.java:257)
  at org.glassfish.persistence.jpa.JPADeployer.event(JPADeployer.java:199)
  at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
  at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:419)
  at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:242)
  at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:351)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:354)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:369)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1077)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1226)
  at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1215)
  at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:375)
  at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:209)
  at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
  at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
  at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
  at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:817)
  at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:718)
  at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1007)
  at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
  at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
  at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
  at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
  at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
  at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
  at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
  at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
  at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
  at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
  at java.lang.Thread.run(Thread.java:680)

Caused by: java.lang.RuntimeException: Uncompilable source code - class <error> is public, should be declared in a file named <error>.java
at com.scholar.entity.<error>.<clinit>(FriendWith.java:22)
... 43 more

如果你查看堆栈跟踪的底部,你可以看到它说FriendWith line 22 有问题。没有FriendWith.java。有没有办法来解决这个问题。我清理并构建项目文件夹,重新启动服务器,重新启动计算机,但它没有修复它

【问题讨论】:

    标签: jpa jakarta-ee


    【解决方案1】:

    即使您删除了 FriendWith.java,也有可能您留下了 FriendWith.class,而 JPA 包正在某处找到它。

    在您的 jars、wars、ears 或其他任何东西以及您的文件系统中搜索类文件。如果您要将构建的项目复制到“部署”位置,请确保 .class 文件不在部署区域中。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2011-03-25
      • 2013-05-01
      • 2021-07-06
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多