Re: [eclipselink-users] TopLink to EclipseLink migration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] TopLink to EclipseLink migration

From: jamesssss <jamesssss@xxxxxxxxx>
Date: Thu, 1 Nov 2012 07:04:16 -0700 (PDT)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

It could be a bug.  Try to isolate a test case and log a bug.

You might be able to change your usage of the nested unit of works to avoid
the issue.  Try getting the changes for the nested unit of work before
commit and see if it has detected the change.  It could be an issue with
merging not being able to match the new object.  Ensure the new object's id
has been assigned.




--
View this message in context: http://eclipse.1072660.n5.nabble.com/TopLink-to-EclipseLink-migration-tp155391p155450.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.

Prev by Date: Re: [eclipselink-users] remove boiler plate code in POJO that does JPA
Next by Date: [eclipselink-users] Question about weird paging behavior
Previous by thread: [eclipselink-users] Is there a way by which we can map the same column to multipe embedded attribute overrides ?
Next by thread: [eclipselink-users] Question about weird paging behavior
Index(es):
- Date
- Thread

Breadcrumbs