Community
Participate
Working Groups
We should provide an option to deploy/connect session when EntityManagerFactory created, not EntityManager. Currently we deploy when the em is first accessed, this makes the server start quicker, but means the first request could take a very long time, and possibly timeout. It also causes an issue that each connection pool is validated on connect, binding each to the current JTA transaction. This will break if a LLR optimization is being used.
Created attachment 192320 [details] patch - various bug fixes
SVN trunk pending commit: Bug#341153 - allow deploy to occur at startup https://bugs.eclipse.org/bugs/show_bug.cgi?id=341153 Also, Bug# 337375, 271636, 337585, 340765, 340860 Code review: Andrei, pending Changes: - Added "eclipselink.deploy-on-startup" option to deploy and connect persistence unit when factory is created, instead of when first entity manager to avoid JTA issues with multiple connections. - Fixed bug in batch fetching using IN when multiple pages are required. - Fixed bug in partitioning to use default connection instead of all write connections. - Added test for field access to interface impl. - Added batch fetch tests. - Fixed annotation processing to use correct weaving flags.
fixed
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink