Almost impossible to subclassing DetachedCriteria

Description

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.

Environment

3.2 cr2

Activity

Show:
Brett Meyer
December 18, 2013, 8:19 PM

The Criteria API is considered deprecated

Assignee

Unassigned

Reporter

Luciano Greiner dos Santos

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure