So, 4.3.0.Beta4 is almost two months past its due date now, this bug is almost five months old, and it would seem that nobody from Hibernate has even acknowledged that it exists. It's not assigned to anyone, it's not assigned to any particular release, and its priority is woefully inadequate. This bug is a BLOCKING issue, not merely a major issue. There's an entire feature of JPA that's simply non-functional, despite the Hibernate website's assertion that only entity graphs are incomplete. I would think they had all been kidnapped, except that there's plenty of activity on GitHub.
There are probably plenty of people following this bug who, like me, would be more than happy to submit a pull request to fix the issue because they need it fixed so badly. But without even so much as a response from a Hibernate team member, I don't even know where to start. I have debugged this issue for hours, but there's so much indirection going on that I just simply don't know the codebase well enough to blindly make a change that could break 100 other things without my even knowing it.
|