[ https://hibernate.onjira.com/browse/HHH-4417?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-4417: ------------------------------------- Even in {{hbm.xml}} binding, it is just assumed that whatever is named as a {{collection-type}} deals with the matching Java type named by the containing {{<list/>}}, {{<set/>}}, etc. As far as the corollary to determining difference between {{<list/>}}, {{<set/>}}, etc {{CollectionBinder}} on the annotation side already contains the appropriate logic. As Endre points out, there is a minor issue WRT the "Commons Annotations" stuff and/or the ReflectionManager where custom collection implementations (not the collection type implementations!) are not recognized as collections, even if the custom collection implementation extends a JDK one. So you have to expose this as a java collection ATM :( As an example: {code:borderStyle=solid} // given: class MyCustomList<X> implements java.util.List<X> { ... } // and: class MyCustomListType implements UserCollectionType { ... } // works fine @OneToMany(...) @CollectionType( type="MyCustomListType" ) public List getOrders() // erros due to mentioned limitation @OneToMany(...) @CollectionType( type="MyCustomListType" ) public MyCustomList getOrders() {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira