Container over eclipseLink ORM interface.
It seems that EclipseLink is terribly underrated, compared to Hibernate. It comes with much better session management architecture and, when properly used, is much faster than Hibernate, yet extremely simple to configure.
Our container now supports filtering and sorting by Vaddin Container API and additionally by Expression objects. It caches it's element's indexes to improve performance, as well as optimizes object fetching to maximize probability of EclipseLink's cache hits.
Moreover, it reads class meta data from EclipseLink engine, so persistence can be configured in whatever way you want (EclipseLink lets you do it by annotations, XML configuration, class descriptors, or any mix of above).
- Container itself (Abstract + Implementation that use static class to access Session)
- Interfaces and sample classes used to provide container with Session access
- Application Servlet with code that preconfigures database access (sample setup code)
NOTE TO USERS: If You are using it, find a bug etc. - let us know on the forum.