[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138?page=c...
]
Cameron Beccario commented on HHH-5138:
---------------------------------------
The @deprecated comment in org.hibernate.Hibernate led to this JIRA issue, but it is not
clear what the deprecated items (in particular, Hibernate.STRING and
Hibernate.BIG_DECIMAL) have been replaced with. What should I now use to make the
deprecated warnings go away?
Redesign types + introduce TypeRegistry & TypeResolver
------------------------------------------------------
Key: HHH-5138
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138
Project: Hibernate Core
Issue Type: Improvement
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.6.0.Beta1
Time Spent: 78h
Remaining Estimate: 0h
Work in progress. The general idea is to have 3 levels of types:
1) What I am tentatively calling a StaticType. These are basic mappings between standard
java types and basic sql types. They require no access to a Session nor SessionFactory to
fulfill their contracts.
2) Scoped. This is mainly the current Type contract, except that these will be
explicitly scoped to a TypeRegistry (which is part of the Configuration and
SessionFactory). Users can provide overrides of these.
3) User types. Again, mainly the current user types contracts.
--
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