-->
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: @NamedNativeQuery , why only once pro entity
PostPosted: Mon Jul 13, 2009 7:41 am 
Newbie

Joined: Mon Jul 13, 2009 7:37 am
Posts: 1
hi,

as the topic says I have a case where my entity is result of N search criteria, and different selects are needed to get this results. I don't understand why is the @NamedNativeQuery allowed only once pro entity and even why it is supposed to be in the entity itself, after all we specify resultClass so it might as well be anywhere.

Please enlighten me. Till then I plan on creating 6 dummy entities just to be holders for the @NamedNativeQuery - ies. And that I don't find very elegant.

Cheers


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.