| RE: [eclipselink-users] EclipseLink 2.1 Planning |
|
My organization would like that existing bugs are taking
care in priority. I’m able to list bugs that are known for years. A good example is that EclipseLink, which is the
reference implementation of JPA, is not JMS specification compliant in its
implementation of cache synchronization -> http://forums.oracle.com/forums/thread.jspa?messageID=3406370� I have provided patches for some bugs and would like they
are committed more promptly: -
270762 CommitManager.initializeCommitOrder create
random order so DB deadlock -
267701 Need clear access to sequencing functionalities
for unmanaged use case -
283767 Provide reasonable hook
to extends EntityManagerImpl I have find the code bug for some issues, that should not
be hard to take care of many of them during a single day of dedication to bug
fixing: -
245726 Need coherent implementation of read-only query -
274417 Allow
PersistenceProvider derived class to use persistence.xml from any location and
using any name - -
281518 Optimization use to
locate assigned UOW to current transaction is broken -
281532 JPA integration broke
migrated code using session.getActiveUnitOfWork() -
281569 Integration of JPA using
transaction-type="JTA" but without EJB container, set-up incomplete
commit cleanup -
286425 Default java.util.Date
conversion doesn't support derived class of Date -
288864 CacheKey.equals could be
faster -
290570 Need more generic hook
than SessionCustomizer.handleException because not called by merge APIs -
294259 Duplicate existence
checks in same UOW -
297155 ObjectLevelReadQuery.CheckCacheOnly
do not return new registered object present in the UOW -
297908 Version check for
Optimistic Locking is not respected and configuration error or warning
generated when using batch writing without binding on Oracle DB Future work could be driven by themes like: -
Apply faster submitted
patches -
Fix faster bug having
a solution description -
Fix old functional bugs, see above -
Fix performance bottleneck: o
288864 CacheKey.equals could be
faster o
294259 Duplicate existence
checks in same UOW o
297908 Version check for
Optimistic Locking is not respected and configuration error or warning
generated when using batch writing without binding on Oracle DB (Faster
configuration found on real system) o
Don’t flush when the
query can conform in memory o
Don’t invalidate query
cache when no modification can impact the query result o
Duplicate SQLs, and
duplicate table in from clause when using eager loading -
Set default to thread
safe code and query returning right result, to help usability for new user. And
avoid expert find out the wrong default in production: o
Fix JMS based
propagation of changes o
286425 Default
java.util.Date conversion doesn't support derived class of Date o
Fix Calendar cloning
and change detection o
Default to conform in
unit of work to not get wrong query result o
245726 Need coherent implementation of read-only
query From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Douglas Clarke Sent: Monday, November 30, 2009 9:17 PM To: Eclipselink-Dev (E-mail); Eclipselink-Users (E-mail) Subject: [eclipselink-users] EclipseLink 1.2 Planning EclipseLink Users, Contributors, and Committers, We are wrapping up EclipseLink 2.0 now and need to start
working towards EclipseLink 2.1 which will be our Helios release in June. We
have accomplished a lot in the last year around standards delivering the
reference implementation of SDO 2.1.1 and now JPA 2.0 as well as addressing
JAXB 2.1 compliance and many advanced capabilities in all areas of the project.
Over the next 2 weeks we need to formalize our 2.1 themes and requirements.
Peter and I have started a wiki page for this purpose: http://wiki.eclipse.org/EclipseLink/Development/2.1 We are asking all interested parties to help us shape
what is coming in the 2.1 release as well as future releases by participating
in the process. Please make sure your issues and enhancement requests are
captured in bugs with clear descriptions and actionable outcomes. We will be
basing our work for this next cycle on the themes we agree upon in an upcoming
committer meeting as well as the bug backlog in bugzilla. Make sure if you want
an issue addressed that you vote for the bug and/or start a thread on the forum
to discuss how the project should address your requirements so that others can
become aware of the issue and the bug number so they can vote as well. As always, bugs with patches supplied will be prioritized
as we greatly appreciate the additional effort it takes to contribute. All
feedback on this process and the project in general is appreciated. Cheers, Doug Clarke & Peter Krogh EclipseLink Project Leads |