Comments on: JPA 2.0 Typesafe Criteria API and Annotation Processing Howto

By: Gregory Shrago

Gregory Shrago — Tue, 09 Mar 2010 13:54:11 +0000

Annotation Processing is integrated into compiler pipeline thus things could not get out-of-date silently as regeneration is performed on each comile/make/build all. The whole purpose of a separate “Process Annotations” action is to forcibly regenerate sources when Java compilation is undesirable i.e. a project doesn’t compile but we would like to have completion/navigation/etc. for JPA metamodel.

By: Noah

Noah — Thu, 04 Mar 2010 17:01:42 +0000

Gregory,

Thanks for the information. I’ll try the simple “Compile” action. Your point is taken about mixing the generated and static sources. Things could get silently out-of-date if you don’t have the auto generation wired up via ant/ipr/maven or some other automatic mechanism when you compile.

-Noah

By: Gregory Shrago

Gregory Shrago — Thu, 04 Mar 2010 16:11:42 +0000

As described here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=302450
EclipseLink processor expects persistence.xml in CLASS_OUTPUT (which is wierd) thus preventing “Process Annotations” action from working correctly but simple “Compile” action works fine if the persistence.xml is under some source root/META-INF/. I’ve checked it with eclipselink.persistencexml=META-INF/persistence.xml option.

We’ve added the warning about generated_src directory clearing in settings dialog and we have changed the “Process Annotation” action (will be available in the next EAP).
One should never mix real sources and generated ones otherwise it is not possible to “rebuild all” correctly.

By: Gregory Shrago

Gregory Shrago — Wed, 03 Mar 2010 16:32:29 +0000

There is indeed a problem. We are working to make CanonicalModelProcessor happy. It appears to be very restrictive when it comes to paths.

By: Noah

Noah — Tue, 02 Mar 2010 15:01:49 +0000

Hi,

I tried setting things up for Eclipselink but the Build -> Process Annotations menu remains grayed out after completing these steps. When I rebuilt my project it deleted my src directory since I had tried to point the generated classes folder to my src folder so that the generated classes would be side by side with the entity classes. so I can check them in. There should definitely be a warning that it deletes that directory!

I’m not sure what IDEA is setting the processors working directory to but in the case of Eclipselink I have one processor run option set like so:

eclipselink.persistencexml=web/META-INF/persistence.xml but when I rebuild the project I get an error saying “Unable to load persistence.xml G:\sandbox\trunk\myproject\build\production\myproject\web\META-INF\persistence.xml”

I tried changing the value if the option to be a relative path from the build\production\myproject folder back to my persistence.xml file like so:

eclipselink.persistencexml=../../../web/META-INF/persistence.xml

but that gave me the following error:

java.lang.IllegalArguementException: relativeName is invalid

Has anyone set this up with Eclipselink? BTW, I can generate them by hand on the command link with “javac -processor org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor …” so I know I have my options and classpath information correct and I am just not understanding the magic to make IDEA happy. Thanks,

-Noah

By: Peter

Peter — Sat, 12 Dec 2009 16:48:38 +0000

Does anybody know how to debug annotation processors in IDEA?

By: Gregory Shrago

Gregory Shrago — Mon, 30 Nov 2009 13:39:01 +0000

The generated sources are indexed if the ‘generated’ directory is marked as a source folder in the corresponding module settings. Anyway Peter is right that currently IDEA does not do anything with the generated classes.

By: Timo Westkämper

Timo Westkämper — Thu, 26 Nov 2009 12:58:00 +0000

If your are unhappy with the JPA2 APT metamodel, you should given Querydsl a try. It provides a more compact, readable and typesafe metamodel :

http://source.mysema.com/display/querydsl/Querydsl

By: Peter

Peter — Thu, 26 Nov 2009 12:47:09 +0000

I really appreciate that feature. However unless the generated classes are recognized by the IDEA and the generated sources are indexed and included into the type hierarchy it’s pretty useless

Guess this will come in a later milestone of Maia

By: B. K. Oxley (binkley)

B. K. Oxley (binkley) — Thu, 19 Nov 2009 16:25:12 +0000

I have the same question as David Vallner, re:

http://projectlombok.org/features/Data.html

I’d like to have IDEA recognize the generated classes, and no longer give me red squiggles for calling generated methods (getters/setters in this case). Navigation to the generate class would be a bonus.