Why can't I do this:

???

I'm doing this:

but this feels very wrong.

I just wanted to make a method for generic searches.

do not mix entity names ( mandatory when parsing jsql) and parameters

Query q = em.createQuery(String.format("SELECT o FROM %s o WHERE o.%s = ?1", className, attribute));
q.setParameter(1, value);

So, it's a wee bit evil, but you can do this:


Kinda defeats the purpose of having an abstraction like JPA if you're just gonna grab the underlying implementation and muck with it, but what the hell? Depends on what your priorities are.

And if you're in JBoss, using EJBs, you can even do fun stuff like:



and just skip the EntityManager stuff. In my EJBs, I just inject both, and use whichever one's easiest.

Like I said . . . evil, but I'm not migrating to another provider ever, so it's not a big deal.

-Falken

Thank you both.

Unfortunately I am using a JPA implementation that doesn't allow criteria, not Hibernate.

Now I am having this problem: the value field is String but I wanted to pass anything there (string, double, int...). The problem is that setParameter needs to know the actual type of value, or it will return empty when trying to search for a field that is, for example, an integer. So, the question is, is it viable to make such generic search method?