Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I avoid putting FQCN into SELECT NEW ...?
Packages are often changed during refactoring, and that may cause troubles.
Not sure if I can do something for that in JPA; I am also happy with Hibernate 3.6 solution (Ejb3Configuration).
Note that class used in SELECT NEW is not an entity, so standard trick with <class> in persistence.xml doesn’t work (YMMV).
As per the spec, the constructor name has to be fully qualified, JPA spec 4.8.2. So no, you can’t avoid it. And why can’t you just use MyClass.class.getName() and hence cope with refactorings?