我开发了一个使用EclipseLink进行持久化的servlet。
当应用程序启动时,我在服务器日志中重复多次获得以下消息:
12:17:45,586 WARN [org.eclipse.persistence.metadata] (MSC service thread 1-1) Reverting the lazy setting on the OneToOne or ManyToOne attribute [CategoryCode] for the entity class [class se.magos.domain.Site] since weaving was not enabled or did not occur.
12:17:45,825 INFO [org.eclipse.persistence.connection] (MSC service thread 1-1) vfs:/C:/Dev/Applications/JBoss/jboss-as-7.1.1.Final/standalone/deployments/Ear.ear/Persistence-1.0-SNAPSHOT.jar/_foo login successful
12:17:45,891 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:45,894 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:45,896 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:45,898 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:45,900 WARN [org.eclipse.persistence] (MSC service thread 1-1)
...and it goes on and on...
12:17:46,091 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:46,093 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:46,097 WARN [org.eclipse.persistence] (MSC service thread 1-1)
12:17:46,236 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015951: Admin console listening on http://127.0.0.1:9990
它接近域和服务对象的数量并且结合但不完全。
这条日志消息的原因是什么?如何摆脱它?
答案 0 :(得分:0)
JBoss AS 7不使用EclipseLink作为JPA实现。它默认使用Hibernate。但是有一个article解释了如何将EclipseLink与JBoss AS 7一起使用。
但我鼓励您使用JPA,因为它比使用供应商特定的JPA实现更便携。