From: Luciano G. d. S. (JIRA) <no...@at...> - 2006-08-02 20:04:16
|
Almost impossible to subclassing DetachedCriteria ------------------------------------------------- Key: HHH-1964 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1964 Project: Hibernate3 Type: Improvement Components: query-criteria Versions: 3.2.0.cr3 Environment: 3.2 cr2 Reporter: Luciano Greiner dos Santos Hi. I am developing a new Architeture for a telecom company, and it will user Hibernate as ORM abstraction. I did a DetachedCriteria generator, and it worked well unless for some subcriterias issues. I looked at DetachedCriteria source file and i thought it would be easier to extend it or create a new implementation based on its interface. Well, but DetachedCriteria is a class, not an Interface and it does not implement an operations interface. Well, so i could just subclass it, but it is almost impossible because of its field and method access modifiers. Shouldn't DetachedCriteria be an Interface or at least have an operations Interface so that i can replace its use with my own implementation like Criteria? If it is not possible, couldn't we turn DetachedCriteria class more suitable for subclassing? Thank you, and i am available to help if needed. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |