Jira issue originally created by user romanb:
We should consider allowing the configuration of custom PersistentCollection implementations on a per-association basis.
This could allow users to craft optimized (SQL) behavior for for some of their collections to improve performance without changing the domain model code.
For this, PersistentCollection needs to be designed for inheritance.
Comment created by romanb:
Rescheduled for 2.1. Might be 2.x.
Comment created by @beberlei:
Reschedule for 2.x
Comment created by Wilt:
Any progress on this new feature?
Comment created by @ocramius:
This can't be solved in the 2.x series because of the tight coupling between association UnitOfWork logic and the PersistentCollection API.