Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[2.8.1] QueryDSL JPA on AppEngine not working because of escape character #262
I tried to get querydsl working on AppEngine today. I'm using querydsl via the Spring Data JPA repository support.
As soon as I try to run querydsl filter containing a 'startsWith' I get the below exception.
Could you try the snapshot version 2.8.2.BUILD-SNAPSHOT? You can get it via this repository https://oss.sonatype.org/content/repositories/snapshots/
ObjectManager is a superinterface (http://www.datanucleus.org/javadocs/core/3.0/org/datanucleus/ObjectManager.html), so I guess a safer choice.
I will let you know when a new snapshot is available.
Aha this changed from DataNucleus 3.0 to 3.1
Why http://www.datanucleus.org/javadocs/core/3.1/org/datanucleus/ObjectManager.html is mentioning that the ObjectManagerImpl is a known implementing class I don't know.
Maybe safe to add both
To bad still not working. Need to look into this tomorrow again.
It seems with latest code that mappings until
But I never see
I just tried constructing a JPAQuery with the DataNucleusTemplates.DEFAULT manually.
This is (I assume) similar as
And that worked, it returned a user without any exception.
Now only we need to find why the detection is not working and what is going wrong there.
I think it's really related to this call:
While debugging I can see it go into the Class.forName which is not happening for the previous defines mappings.
And then I end up at
Hmm, maybe the Class.forName for
Maybe good to just catch Exception instead of ClassNotFoundException?
added a commit
Nov 1, 2012
I tried but no difference. While debugging I can see the code now contains the Exception catch instead of ClassNotFoundException.
But the behaviour I see is the same.
As soon as it tries to do
So without even trying to add mapping for
Good point, should have thought about that myself...
I copied al the code of the
Even from the same controller I call
So maybe my querydsl jar was out of sync with the sources jar?
So I removed the .cache form .m2/repository folder togther with com/mysema to make sure everything was ok.
And then it worked.
I was always using mvn with -U option to force a check for updated releases and snapshots on remote repositories but didn't seem to work...
I'm glad this is working nog.