Eclipse Google -App -Engine "DOES NOT IMPROVE"

Question

First Eclipse:

Cannot get rid of this error ... Tried all suggested fixes in google ..

The persistent class "The com.blahb.blahblah.master.UserToken class does not seem to have been extended. You might want to restart the enhancer and check for errors in the output." does not have a table in the database, but this requires an operation. Please check the MetaData specification for this class.

List of 500 lines of exceptions... *Caused by: javax.jdo.JDOUserException: Persistent class "Class com.blahb.blahblah.master.UserToken does not seem to have been enhanced. You may want to rerun the enhancer and check for errors in the output." has no table in the database, but the operation requires it. Please check the specification of the MetaData for this class. at org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:375) at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:230) at com.gulfnet.gulfstar.master.Master.getUserToken(Master.java:645) at org.apache.jsp.top_jsp._jspService(top_jsp.java:68) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at com.google.appengine.tools.development.PrivilegedJspServlet.access$101(PrivilegedJspServlet* 

My colleague has the same project on her Windows PC, and it works great ...

I tried three different computers Linux, Mac, Windows, 3 different versions of eclipse, 20 different import methods, creating a new project, ect ....

Yes, fixed .classpath to display the correct location of all jar files. I tried adding every single class, java, jar, as suggested in one of the google blogs, to class / buildpath (window → pref → google → orm) nothing ...

And where is that damn "Enhancer Console" that should be in Eclipse ...? I am running the latest Eclipse, with all the plugins of Google applications.

Any ideas ...? Anyone?..

Thanks!

Answer 1

The problem is that the Enhancer for DataNucleus is removed from the Builders list for the project. For me, the whole project Clean, rebuilt, etc. Did not help. You need to do the following: (1) Create a new GAE project sample, open the ".project" file of this project in a text editor, copy this text from there:

 <buildCommand> <name>com.google.appengine.eclipse.core.enhancerbuilder</name> <arguments></arguments> </buildCommand> 

Now copy this to the bottom of the builders list in your own .project file. Now DataNucleus should work fine. I have no idea why this sometimes disappears.

Answer 2

We edited the [Project> properties> Google> App Engine> ORM] page to remove src / and only extend a subset of our classes (src / com / vo / .java *, src / com / back /? And res /), like described in: datanucleus enhancer and javaw: "parameter is invalid"

We also copied Google | App Engine for a shorter path, as explained below, for us: http://code.google.com/p/google-web-toolkit/issues/detail?id=4395#c15

Answer 3

Right-click the project, then choose Properties> Builders. Is there a point like "Missing Builder (org.datanucleus.ide.eclipse.enhancerbuilder)" ?

If you are creating a new web application project, make sure that “Use Google Web Toolkit” and “Use Google App Engine” are checked, then go to “Properties”> “Builders” again, then say “Enhancer” instead of “Missing builder” ?

If so, then the solution should probably create a new project from scratch, and then manually transfer the content from the old project to the new one. Just importing an old project into another Eclipse does not work, the enhancer will still not be there.

Answer 4

Updating the latest version of appengine java sdk resolved this for me.

Answer 5

The SDK version has changed me.

Interestingly, I already used the latest version. Going back to the previous version was the only way you could activate the boost step. This was with the gradle script construct.

Answer 6

I had the same error, and in my case, the solution simply made the class unstable by commenting on this line:

 @PersistenceCapable(identityType = IdentityType.APPLICATION) 

Then run my application and get a save error, stop it, uncomment the previous line and run the application again.

Answer 7

This problem was resolved for me by adding a primary key, for example:

@PrimaryKey @Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY) private Long id;