[Hibernate-JIRA] Created: (HHH-6927) Cannot register a type through configuration if the type is parametrized
9:18 a.m.
Cannot register a type through configuration if the type is parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and shared
for all my entities and no parameter is injected at all. Looking a bit deeper I think I
found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 a.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole resolved HHH-6927.
---------------------------------
Resolution: Rejected
@TypeDefs and hbm.xml can *only* deal with classes, not instances. hbm.xml hopefully for
obvious reasons; and annotations can only deal with pre-determinate values.
This registration of instances is by design. And you actually can register different
parameterizations; you simply do it under different registration keys. Look at the
signatures:
* {{public void registerTypeOverride(BasicType type)}}
* {{public void registerTypeOverride(UserType type, String[] keys)}}
* {{public void registerTypeOverride(CompositeUserType type, String[] keys)}}
All 3 cases deal with this notion of registration keys. For {{BasicType}} it is defined
on its contract. I could easily be talked into a corollary contract for user types,
something like:
{code}
public interface Registrable {
public String[] getRegistrationKeys();
}
{code}
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Stephane Nicoll commented on HHH-6927:
--------------------------------------
Hi Steve,
Thanks for the quick reply. I had a a look to these methods once again to make sure I did
not miss anything and I don't really understand how registration keys are related to
my problem.
Consider the following use case:
{code:xml}
@Type(type = "MyUserType", parameters =
@Parameter(name = "myParam", value = "myValue")
)
private SomeObject foo;
{code}
Actually the user type needs the actual class of the object it is mapping. Consider
SomeObject a subclass of some base class, the user type is generic for any subclass of
that base class but it needs to know the actual subclass type to work properly when
retrieving the instance. Since nullSafeGet or the userType itself does not provide that
value we have to pass it as a parameter.
Anyway, I want to register a type "MyUserType" for that user type. I can't
use these methods because If I do that, an instance is not injected with the parameter I
need. I believe that you're saying I should register one user type per subclass of the
type I have and assign a registration key to that specific instance. If that's what
you mean, fine considering that you can have all those combinations.
What if if you don't? After all, if you look at my sample above, I just want to do
what I can do through hbm or annotation configuration.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:15 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Stephane Nicoll commented on HHH-6927:
--------------------------------------
In other words, you're saying that registration key equals User type class +
parameters. That's fine by me but if you don't know all the possible combinations
in advance, what do you do?
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole commented on HHH-6927:
-------------------------------------
I understand what you want. But you are mixing 2 different concepts.
In this code sample, you have an inline type def. Think of a type def as a template for
creating type instances. Again, that is not the purpose of {{registerTypeOverride}}. To
date we do not really have a way to "programatically" define/provide type defs.
Mainly because it is already exposed and available by the 2 means you already mentioned.
I completely fail to see what allowing you to do the "type def class name"
registration programatically really buys you.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole commented on HHH-6927:
-------------------------------------
{quote}
In other words, you're saying that registration key equals User type class +
parameters. That's fine by me but if you don't know all the possible combinations
in advance, what do you do?
{quote}
Thats not really what I am saying at all. Like I said before, you are mixing 2 concepts.
You are a type and a type def. Again, think of a type def are a template or pattern for
creating types. A type is a type.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:26 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Stephane Nicoll commented on HHH-6927:
--------------------------------------
Well, that I don't need a @TypeDefs in a each base class that want to use my custom
type?
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole commented on HHH-6927:
-------------------------------------
You don't have to put it in each class.
Type defs defined in an hbm.xml are globally available.
I believe @TypeDef is scoped, however you can define @TypeDefs at package level as well.
If you would really like a means to register a type def with configuration, then open a
*feature request*, but this is clearly not a bug.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Stephane Nicoll commented on HHH-6927:
--------------------------------------
Okay, fair enough. Thanks Steve.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:36 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole commented on HHH-6927:
-------------------------------------
A clarification...
Type defs defined in an hbm.xml are globally available but you must make sure to add that
hbm.xml to the Configuration before you add any other hbm.xmls or annotated entities that
use those type defs.
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:26 p.m.
New subject: [Hibernate-JIRA] Reopened: (HHH-6927) Cannot register a type through configuration if the type is parametrized
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole reopened HHH-6927:
---------------------------------
Cannot register a type through configuration if the type is
parametrized
------------------------------------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6927) Allow registering type defs via Configuration
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Steve Ebersole updated HHH-6927:
--------------------------------
Component/s: metamodel
Issue Type: New Feature (was: Bug)
Summary: Allow registering type defs via Configuration (was: Cannot register a
type through configuration if the type is parametrized)
Stephane, I went ahead and just converted this issue to a RFE. If you do not really care
about this or do not really want it go ahead and close this issue.
Allow registering type defs via Configuration
---------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: New Feature
Components: core, metamodel
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:27 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6927) Allow registering type defs via Configuration
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927?page=c...
]
Stephane Nicoll commented on HHH-6927:
--------------------------------------
Interested. Thanks.
Allow registering type defs via Configuration
---------------------------------------------
Key: HHH-6927
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6927
Project: Hibernate Core
Issue Type: New Feature
Components: core, metamodel
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Since I don't want to hardcode @TypeDefs in each class hierarchy that uses a custom
type, I am using the {{cfg.registerTypeOverride}} method. This works fine for simple user
type but I have a parameterized user type.
In that case, using this method leads to a single user type instance being used and
shared for all my entities and no parameter is injected at all. Looking a bit deeper I
think I found the culprit in TypeResolver.
{code:java}
public Type heuristicType(String typeName, Properties parameters) throws MappingException
{
Type type = basic( typeName );
if ( type != null ) {
return type;
}
try {
Class typeClass = ReflectHelper.classForName( typeName );
if ( typeClass != null ) {
return typeFactory.byClass( typeClass, parameters );
}
}
catch ( ClassNotFoundException ignore ) {
}
return null;
}
{code}
base(typeName) will actually return the type that I have registered. Notice that basic
does not take the {{parameters}} argument into account. Since it's not null it just
returns that type.
Maybe I did something wrong. I was surprised that cfg actually registers *instances* and
not classes. Both @TypeDefs and hbm.xml specifies classes. Maybe adding an option to
register a class programmatically?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4766
days inactive
4766
days old
hibernate-issues@lists.jboss.org
12 comments
2 participants
participants (2)
-
Stephane Nicoll (JIRA) -
Steve Ebersole (JIRA)