For example I have such query:
Query q = sess.createQuery("from Cat cat");
List cats = q.list();
If I try to make something like this it will show warning "Type safety: The expression of type List needs unchecked conversion to conform to List":
List<Cat> cats = q.list();
Is there a way to avoid it?
Apparently, the Query.list() method in the Hibernate API is not type safe "by design", and there are no plans to change it.
I believe the simplest solution to avoid compiler warnings is indeed to add @SuppressWarnings("unchecked"). This annotation can be placed at the method level or, if inside a method, right before a variable declaration.
In case you have a method that encapsulates Query.list() and returns List (or Collection), you also get a warning. But this one is suppressed using @SuppressWarnings("rawtypes").
The listAndCast(Query) method proposed by Matt Quail is less flexible than Query.list(). While I can do:
If I try the code below:
I'll get a compile error: Type mismatch: cannot convert from List to ArrayList
A good solution to avoid type safety warnings with hibernate query is to use a tool like TorpedoQuery to help you to build type safe hql.
Using
@SuppressWarnings
everywhere, as suggested, is a good way to do it, though it does involve a bit of finger typing each time you callq.list()
.There are two other techniques I'd suggest:
Write a cast-helper
Simply refactor all your
@SuppressWarnings
into one place:Prevent Eclipse from generating warnings for unavoidable problems
In Eclipse, go to Window>Preferences>Java>Compiler>Errors/Warnings and under Generic type, select the checkbox
Ignore unavoidable generic type problems due to raw APIs
This will turn off unnecessary warnings for similar problems like the one described above which are unavoidable.
Some comments:
Query
instead of the result ofq.list()
because that way this "cheating" method can only be used to cheat with Hibernate, and not for cheating anyList
in general..iterate()
etc.We use
@SuppressWarnings("unchecked")
as well, but we most often try to use it only on the declaration of the variable, not on the method as a whole:No, but you can isolate it into specific query methods and suppress the warnings with a
@SuppressWarnings("unchecked")
annotation.If you don't want to use @SuppressWarnings("unchecked") you can do the following.
FYI - I created a util method that does this for me so it doesn't litter my code and I don't have to use @SupressWarning.