Any news on this issue?.

I'm currently working with a polymorphic relationship between documents and print versions. There are many types of documents, but they all share the same characteristics when they are printed (eg. filename, file hash). Creating one subclass per document would be tedious (DocumentPrint1, DocumentPrint2 .... DocumentPrintN). This is where mapping an interface is great, but the fact that I can't associate and navigate the relationship is really annoying. I would have to always lookup all the printings to find a specific document.
If the MetaType and the @JoinColumn FK act as a Composite FK, why they can't be joined to make @AnyToMany work?Doesn't seem to hard to accomplish, instead of joining with one column, you join with two. Just looks like another kind of EmmbededId.