Hide Forgot
Description of problem: Method org.jbpm.logging.exe.LoggingInstance.getLogs() has changed. It now returns an umodifiable collection. This causes the following two tests to fail org.jbpm.identity.assignment.ExpressionAssignmentHandlerTest.testFirstTermVariableUser org.jbpm.identity.assignment.ExpressionAssignmentHandlerTest.testFirstTermVariableGroup with message: ava.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1028) at org.jbpm.identity.assignment.ExpressionAssignmentHandlerTest.deleteLogs(ExpressionAssignmentHandlerTest.java:163) at org.jbpm.identity.assignment.ExpressionAssignmentHandlerTest.testFirstTermVariableUser(ExpressionAssignmentHandlerTest.java:142) at org.jbpm.db.AbstractDbTestCase.runTest(AbstractDbTestCase.java:73)
Marek, This _was_ a problem, but I'm pretty sure I fixed it: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbpm/jbpm3/branches/jbpm-3.2-soa/core/src/main/java/org/jbpm/logging/exe/LoggingInstance.java?r1=7060&r2=7072 See https://svn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.12/core/src/main/java/org/jbpm/logging/exe/LoggingInstance.java as well, where this is: /** * If you modify the returned list in any way, you run the risk * of causing exceptions in a concurrent situation. * * @return The list of logs */ public List getLogs() { return logs; } Maybe mead or the build grabbed it too early? (or did I miss something?)
Yes this one is related to the build process. It grabbed revision 7071. Thanks Marco
Looks done, low priority.
Verified on ER2.