TopLink 10g Cascading Issue

Question

How can I make the default read behavior of each Entity set to **lazyloading** in TopLink 10g?
We're using TopLink 10g in an application which is being used by 1000s of customers everyday. I'm also looking to find a good and safe way to migrate from TopLink 10g as there are very few stuffs available about TopLink 10g and those who were using it already migrated to EclipseLink/JPA or TopLink 11g-12g. We also have to do the same, but that will be a long-term goal. Please share your experiences regarding migration from TopLink (10g).
Although, for now, we need to fix a problem (which would be a quick-fix instead of migrate from TopLink 10g). The problem is; One of the TopLink Entity read also getting (querying) all of its associates (child Entities) which is causing too many unnecessary queries to the database. However, we solved this problem by using `ObjectCopyingPolicy`:
    ObjectCopyingPolicy objCopyingPolicy = new ObjectCopyingPolicy();
    objCopyingPolicy.setShouldResetPrimaryKey(false);
    objCopyingPolicy.cascadePrivateParts();
    someEntity = (SomeEntity) getTopLinkTemplate().copy(getTopLinkTemplate().readById(SomeEntity.class, new Long(someId)), objCopyingPolicy);
The aforementioned code snippet is one of the resolution to solve such a problem. But, we'd like to solve this problem by configuration (persistence.xml etc.). There is nothing in the documentation, neither I found anything by googling it.
Please let me know if you would require more details to answer this question.
Good Day!

Answer 1

First are you using JPA and a persistence.xml with TopLink (TopLink Essentials was the JPA provider I believe) or are you using native TopLink with a sesssions.xml?  WIthout entity changes to support lazy relationships (such as weaving if using JPA) lazy relationships will only work for collection mappings - but these are already set to default to lazy,  If it is JPA, you can configure your entity mappings to be Lazy through annotations or an orm.xml file and let weaving work on your entities, while if using Sessions.xml, you need to make changes to the entities themselves to support lazy relationships as well as set the mappings to be lazy.  This is called indirection in TopLink, and is described here: Understanding Relationship Mappings
If you are using JPA and a persistence.xml, the migration to EclipseLink should be fairly easy.  See https://wiki.eclipse.org/EclipseLink/Examples/JPA/Migration/TopLinkEssentials for details
Otherwise it may require package renaming and ensuring that the project was not using deprecated classes, but still should not be too complex.  Migrating from Native TopLink | EclipseLink 2.4.x Understanding EclipseLink has instructions and details.
If this is not enough to go on, please give more details on what you have. 
Best Regards,
Chris