Ideas for a RoadMap of TopLinkEssentials

This is totally uncommitted, just conversation fodder at this point.


From Doug Clarke @ Oracle

We are working on a roadmap that lays out our plans for TopLink Essentials. We are hopefully going to review this with Sun and get it published in the near future. The goals we plan to address in the roadmap include:

  • Improved visibility and brand recognition of TopLink Essentials. We need to be growing the community and user base.
  • High priority ER's filed and voted on in the GF issue tracker
  • Several Advanced/Extended ORM initiatives that will expose functionality beyond JPA

The success of TopLink Essentials is also dependent upon addressing the bugs and enhancement requests of containers other then GlassFish who are leveraging us. We need to try and address what we can and also try our best to ensure our schedule produces functionality that can be included in these container's releases. Addressing these issues and schedules will be challenging.

Currently I am aware of the following containers including or certifying TopLink Essentials as their JPA implementation:

  • GlassFish
  • SunAS
  • OracleAS 10.1.3.1
  • Spring 2.0
  • JEUS (Tmax Soft)
  • EasyBeans - JOnAS EJB 3.0 Container

As far as release/milestone dates we are currently working to the GlassFish schedule since TopLink Essentials is a module of this project.


From Eliot Morrison @ Sun

Here is a list based on Sun's engineers and what we have seen in the mailing list.

  • Performance
    • Batch Writing for Performance
    • Query Compilation caching
    • Query result Cache
    • Change Tracking using Weaving for performance
  • Misc Features
    • Field level Optimistic Locking
    • Pessimistic Locking
    • Timeouts for Queries
    • Maps mapped to Join tables with extra columns
    • Support for FlushMode.MANUAL (aka NEVER)
  • Query Compiler
    • Better validation and error messages
    • Decouple from TopLink model
  • Usability
    • Monitoring
    • Model Validation
    • Improve Error Messages
    • Support for Table Per Class inheritance strategy
    • Support for mixed access type for inheritance and embedded fields
    • Add extra annotations for runtime validation (Hibernate validation style)
  • EE Features
    • Pluggable caching
    • Remote Cache Synchronization
    • EM Passivation
  • Bugs
    • Need to prioritize open bugs
    • Fix re-prioritized P2-P3 Bugs
  • Non TopLink value adds
    • JAXB bridge (HiberJAXB3 perhaps?)

From Wonseok @ TmaxSoft

  • clustered 2nd-level cache
  • configurable cache invalidation policies
  • query cache

From Eduardo Pelegri @ Sun

  • Figure out how to deliver JavaPersistence.next EAs to ensure a high quality specification.

Access Count: (org.goodjava.plugin.hitcounter.HitCounter)