[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-users] Migration failures from el 2.4 to 2.5.2..
|
Found the problem.
We were missing one of the embeddables in the persistence xml file . Lets say we have the following classes. Consider
@Embeddable
public class Foo
{
@Embedded
private Bar bar;
public Bar getBar()
{
return bar;
}
}
in our persistence.xml file we forgot to add the class Bar, so when it was processing Foo it was giving the java.util.ConcurrentModification exception. On further debugging found the following
In 2.4.0 we have the file called org.eclipse.persistence.internal.jpa.metadata.MetadataProject.java and it just had 2 steps - entity accessors, root embeddable accessors .
In 2.5.2 we have the same file that has 4 steps -> entity accessors, root embeddable accessors,converter accessors and embeddable accessors ,
The final embeddable accessors was where it failed. I believe that eclipselink should give a proper error message stating that it’s not able to reference the embedded class instead of the very generic java.util exception.
Thx
Vaidya
Please consider the environment before printing this email and any attachments.
This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.On Tuesday, September 23, 2014, Rick Curtis <
curtisr7@xxxxxxxxx> wrote:
This smells like a bug. Can you put together some sort of a small test that recreates the problem?
Thanks,
RIck