Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] [Fwd: [Bug 248999] 17 JPA tests fail while running against GlassFish]

Hello Darani,

Test changes look fine, but for me, more needs to go into the bug explanation and why these changes are necessary. From the exceptions thrown from the tests in question, Glassfish seems to be wrapping queries in a proxy and then throwing an exception when they get executed - regardless of the EntityManager they are associated to being in a transaction or not. The specification seems to state that the context needs to be in a transaction when the query executes, not when the query is created - otherwise why not throw the exception straight away when an update query is created. To me, this seems like be a bug in the glassfish proxy, not in the tests. Am I missing something?

Best Regards,

Darani Yallapragada wrote:
Please do review the patch for Bug#248999 and let me know if any changes are supposed to be made.



[Bug 248999] 17 JPA tests fail while running against GlassFish
Mon, 29 Sep 2008 14:56:51 -0400 (EDT)

Darani.Yallapragada@xxxxxxx Product/Component: EclipseLink / JPA

--- Comment #1 from Darani Yallapragada <darani.yallapragada@xxxxxxx>  2008-09-29 14:56:54 -0400 ---
Created an attachment (id=113788)
 --> (
FixForBug 248999

The attachment is the diff of "" in which the
queries (deleteQuery) are defined within the transaction in these two methods "testFindDeleteAllPersist()" and "internalTestReadTransactionIsolation(boolean shouldOriginalBeInParentCache,
boolean shouldUpdateAll, boolean shouldRefresh, boolean shouldFlush)"


eclipselink-dev mailing list

Back to the top