I'm about to quit on JPA/JDO after 2 days of pure frustration. The
final straw is:-
System.out.println(emp.dept name= + emp.getDept().getName
());// throws an NPE
vs.
System.out.println(emp.dept name= +
emp.dto.getDept().getName());
The final straw is:-
System.out.println(emp.dept name= + emp.getDept().getName
()); // throws an NPE
So why not address what the difference is in calls to your persistable
class ? Nothing is non-deterministic by definition that you have a
programming language here and rules
I realise that non-deterministic is a relative term, and that given enough
time, reading, research, etc etc I will be able to determine why adding a
println prevents an NPE.
My point (and I think of others) is why?. Especially since it's taken me 2
days already that I was supposed to have spent
De gustibus non est disputandum - if you feel more comfortable with
low-level Api than with JDO/JPA Api it is up to you. You spent two
days trying to cope with Google App Engine JPA/JDO problem, I spent a
lot of sleepless nights migrating my EJB3/JPA application to Google
App Engine keeping
I am not going to talk much about portability part. I believe
everybody undestands that.. and some are ok with continuing with GAE
datastore forever. But there can be changes in the APIs in later
releases of GAE. Your code might working with later releases; but
there can be better ways of doing
Other than productivity, I feel JDO code doesn't have the
expressiveness of the Low Level code. You find yourself with JDO code
adding annotations to influence the code, but these annotations don't
really say what you're trying to do.
Why not give examples of what you mean here?
Using the
Clay, I'm totally agree with you.
JDO limits the great flexibility of datastore, I don't understand why
Google advises agains low-level API.
On Sep 22, 4:17 pm, Clay Lenhart c...@lenharts.net wrote:
I'm using the Low Level API, and I find that the JDO and Low Level
APIs have little
Hi Corneliu!
I also had doubts about using JDO in GAE when I started to work with
it. Especially because I met several bugs and it was annoying and time
wasting to figure out what was going wrong. But then the bugs were
fixed in the next release, so I think the guys are generally doing a
good
Thank you very much for your feedback Marton :)
I hope you don't mind, but i will write some further comments to sustain my
cause.
I also would like to hear the opinion of someone from Google. I know you
guys recommend JDO, but can you give me some arguments against using the low
level API,
