[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394?page=c... ] Diego Pires Plentz updated HHH-2394: ------------------------------------ Fix Version/s: (was: 3.0 rc 1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394?page=c... ] Steve Ebersole commented on HHH-2394: ------------------------------------- I think you are mistaken; this issue has no "fix version' assigned... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394?page=c... ] Manuel Bernhardt commented on HHH-2394: --------------------------------------- Hmmk, I can confirm that this still does not work (@Filter-s are bluntly ignored when specified on a subclass, also for the SINGLE_TABLE strategy, without warning message). It would be a terribly useful feature though, and I would argue that it makes little sense to apply a @Filter on a hierarchy superclass if it involves fields that are defined in a subclass. Is there an ETA on this? Or could someone point me to the correct places to look at to fix it? Not that I have tons of time on my hand, but my workaround involving bytecode manipulation of the superclass (because I can't change its code) leaves a pretty bad aftertaste. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira