-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: metadata-complete and extra non-persisted fields explodes
PostPosted: Wed Nov 28, 2012 11:38 pm 
Newbie

Joined: Wed Nov 28, 2012 11:15 pm
Posts: 2
Location: San Francisco, CA
Hello,

I believe this to be a bug but wanted to ask before filing a Jira.

Given this representative class:
Code:
public class Bob { private Long _id; private java.util.Set<Integer> _extra; }


I have declared the entity metadata-complete="true" and have only specified that the Long should be mapped; I did not specify anything about "_extra" nor do I want it managed by JPA. However, it appears that Hibernate 4.1.8.Final is being "helpful" and scanning all the fields on my class and creating org.hibernate.mapping.Column configurations for them.

Since it correctly could not find any mapping for the Set field, it explodes with the following exception:
Code:
org.hibernate.MappingException: Could not determine type for: java.util.Set, at table: BOB, for columns: [org.hibernate.mapping.Column(_extra)]


I believe this to be an error, but I freely admit that I have not studied all 400 pages of the JPA spec.

Thanks for your time!
-- /v\atthew

p.s. I have a very small example if that would be helpful.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.