| Problems migrating from Toplink Essentials to EclipseLink [message #387767] |
Fri, 08 May 2009 03:46  |
Eclipse User |
|
|
|
We are trying to migrate from Toplink Essentials to Eclipselink 1.1.0. We
are using Oracle AS.
Class Kikkare has OneToMany join to one table, which in turn has several
OneToMany joins. This is the error message we experience:
Begin weaver class transformer processing class
[com/juttu/homma/entities/Kikkare].
Weaver encountered an exception while trying to weave class
com/juttu/homma/entities/Kikkare. The exception was:
java.lang.ArrayIndexOutOfBoundsException: 183
java.lang.ArrayIndexOutOfBoundsException: 183
Begin weaver class transformer processing class
[com/juttu/homma/entities/Kikkare].
Weaver encountered an exception while trying to weave class
com/juttu/homma/entities/Kikkare. The exception was:
java.lang.OutOfMemoryError: Requested array size exceeds VM limit
java.lang.OutOfMemoryError: Requested array size exceeds VM limit
We disabled weaving, and then encountered the following error:
Exception [EclipseLink-7092] (Eclipse Persistence Services -
1.1.0.r3639-SNAPSHOT):
org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot add a query whose types conflict with an
existing query. Query To Be Added: [ReadAllQuery(name="KikkareTop.findAll"
referenceClass=KikkareTop jpql="select o from KikkareTop o")] is named:
[KikkareTop.findAll] with arguments [[]].The existing conflicting query:
[ReadAllQuery(name="KikkareTop.findAll" referenceClass=KikkareTop
jpql="select o from KikkareTop o")] is named: [KikkareTop.findAll] with
arguments: [[]].
If we commented out mentioned query, the same error occured in another
entity.
Any hints where to look at?
If the source of the issues is not evident, I would be happy to post the
entity source code if requested, however it will take some time to
"generalize" them.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03481 seconds
Home