我建立了一个简单的多对多关系帐户:角色,但当我尝试在添加角色后将帐户保存在单元测试中时,我收到UnsupportedOperationException:
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)
at java.util.AbstractList$Itr.remove(AbstractList.java:360)
at java.util.AbstractList.removeRange(AbstractList.java:559)
at java.util.AbstractList.clear(AbstractList.java:217)
at org.hibernate.type.CollectionType.replaceElements(CollectionType.java:502)
at org.hibernate.type.CollectionType.replace(CollectionType.java:582)
at org.hibernate.type.TypeHelper.replace(TypeHelper.java:178)
at org.hibernate.event.def.DefaultMergeEventListener.copyValues(DefaultMergeEventListener.java:563)
at org.hibernate.event.def.DefaultMergeEventListener.entityIsPersistent(DefaultMergeEventListener.java:288)
at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:261)
at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:84)
at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:867)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:851)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:855)
at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:686)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:240)
at $Proxy33.merge(Unknown Source)
at org.springframework.data.jpa.repository.support.SimpleJpaRepository.save(SimpleJpaRepository.java:360)
at ....JpaProvider.save(JpaProvider.java:161)
at ....DataModelTest.testAccountRole(DataModelTest.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:240)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:180)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
这里出了什么问题?是我的实体设置有问题,还是由于Hibernate或JPA的限制,迫使我将m:m关系拆分为3个1:n关系,同时对m:n关系表建模(我希望避免这种情况,因为它没有任何附加信息)。我在原型中对其他1:n实体建模,到目前为止似乎效果不错......
这是我的设置,任何想法是否可能是错误的赞赏。
实体(简化):
@Entity
@Table(name="account")
public class Account extends AbstractPersistable<Long> {
private static final long serialVersionUID = 627519641892468240L;
private String username;
@ManyToMany
@JoinTable( name = "account_roles",
joinColumns = { @JoinColumn(name = "account_id")},
inverseJoinColumns={@JoinColumn(name="role_id")})
private List<Role> roles;
public List<Role> getRoles() {
return roles;
}
public void setRoles(List<Role> roles) {
this.roles = roles;
}
@Entity
@Table(name="role")
public class Role extends AbstractPersistable<Long> {
private static final long serialVersionUID = 8127092070228048914L;
private String name;
@ManyToMany
@JoinTable( name = "account_roles",
joinColumns={@JoinColumn(name="role_id")},
inverseJoinColumns={@JoinColumn(name="account_id")})
private List<Account> accounts;
public List<Account> getAccounts() {
return accounts;
}
public void setAccounts(List<Account> accounts) {
this.accounts = accounts;
}
单元测试:
@TransactionConfiguration
@ContextConfiguration({"classpath:dw-security-context-test.xml"})
@Transactional
@RunWith(SpringJUnit4ClassRunner.class)
public class DataModelTest {
@Inject
private AccountProvider accountProvider;
@Inject
private RoleProvider roleProvider;
@Before
public void mockAccountRolePermission(){
Account account = MockAccount.getSavedInstance(accountProvider);
Role role = MockRole.getSavedInstance(roleProvider);
}
@Test
public void testAccountRole(){
Account returnedAccount = accountProvider.findAll().get(0);
returnedAccount.setRoles(Arrays.asList(roleProvider.findAll().get(0)));
accountProvider.save(returnedAccount);
}
}
模拟帐户(与模拟角色相同):
public class MockAccount {
public static Account getInstance(){
Account account = new Account();
account.setUsername(RandomData.rndStr("userName-", 5));
return account;
}
public static Account getSavedInstance(AccountProvider accountProvider){
Account account = getInstance();
accountProvider.save(account);
return account;
}
}
最后,供应商:
@Repository
public class AccountProvider extends JpaProvider<Account, Long> {
}
其中JPAProvider只是封装了许多JPARepository方法(至少在本例中是重要的):
public abstract class JpaProvider<T extends Object, ID extends Serializable> implements JpaRepository<T, ID>, JpaSpecificationExecutor<T>, QueryDslPredicateExecutor<T> {
...
}
关于为什么保存可能是不支持的操作,您有什么想法?
3条答案
按热度按时间eblbsuwk1#
是因为你
这将创建一个不可修改的列表(实际上,是一个不可调整大小的列表)。Hibernate似乎期望一个可修改的列表。尝试使用以下代码:
这个解决方案不会解释为什么会出现另一个异常(可能在Hibernate文档中有记录),但它可能是一个有效的解决方案。
wnvonmuf2#
Hibernate的
Collection
持久化变体试图委托给一个抽象基类(PersistenceBag
),而这个抽象基类没有实现add
方法。ttcibm8c3#
我也遇到过这个问题,根据堆栈跟踪推测这个问题是因为集合是不可变的。这是在看到这篇文章之前。然而,我花了几个小时尝试各种解决方案,但无法绕过这个异常。
这并不是说Lukas Eder所接受的答案不正确,我的问题是我试图持久化的对象集在每个对象(关系对象)中也有集合;因此,我必须用可变集合重新初始化每个子集合,然后才能绕过异常。
奇怪的是,在我的例子中,在生产代码中,这些子集合是不可变的,saveAll()工作正常,但在我的(JUnit)测试上下文中,抛出了异常。