|Re: Toplink 10.1.3.5.0 to EclipseLink 2.4 [message #1009813 is a reply to message #1009731]
||Fri, 15 February 2013 14:15
| Chris Delahunt
Registered: July 2009
This is a large project, probably too large to really go through in forum posts, so I would suggest going through support if you have not already where they can go over the conversion and mappings in detail and compare each setting in the two projects. Otherwise, I'd suggest breaking it down to a smaller test. Maybe a simple app that has one or two descriptors that you port over to EclipseLink. If it shows the same performance problem, then it is much easier to debug and find options and problems. Otherwise, then you know it is likely a conversion issue and can try narrowing down where in your app the problem might be.|
For instance, do the problems occur with specific queries on specific classes, or is it every query, even simple find by primary key queries?
As for porting to JPA - EclipseLink allows using native mappings and sessions through JPA EntityManager API.
Powered by FUDForum
. Page generated in 0.01715 seconds