| Summary: | testNonPooledConnection() failed on Spring with "Test problem: connection should be not pooled" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Yiping Zhao <yiping.zhao> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | andrei.ilitchev | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Yiping Zhao
Created attachment 186437 [details]
test patch
It seems that there is no way to pass EntityManager properties to a managed EntityManager in Spring: like app. server JTA case transaction is required to wrapped EntityManagerImpl to appear Spring's EntityManager wrapper; but unlike app. server JTA case, Spring immediately acquires connection on begin transaction therefore passing of connection properties after beginTransaction is too late - connection is already has been acquired.
In Spring case the test uses app. managed entity manager.
Fixed in trunk. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |