| And again, to be clear, Steve: This was _already_ the way it worked in Hibernate. Hibernate _already_ respected {{<exclude-unlisted-classes>}} in SE environments. All I did was report a _bug_ in that it was _improperly parsing_ {{<exclude-unlisted-classes>}}, and then I provided a patch for that _bug_. If Hibernate wants to stop respecting {{<exclude-unlisted-classes>}} in SE environments, that would be a feature change. It would not be a bug, because the the spec allows it. I would strongly disagree with that change (actually, I would abandon Hibernate completely and switch to EclipseLink if that decision was mode) , but it would not be a bug . However, as it was at the time I reported this _bug_, Hibernate _did_ have this feature and the feature was malfunctioning.
|
