Re: JPA for GWT

I completely agree with this point ! It should be fast enough so that browser doesn't seem sluggish.

Arnaud

2013/11/27 Jens <jens.nehlmeier@gmail.com>

• You can only execute very simple queries,
• You cannot use any joins or nested attribute retrieval,
• All queries should be parsable at compile time. That means you cannot generate dynamic queries during your application run,
• Transactions are not possible,
• You can have only one persistence context,
• The GROUP BY clause is not supported...

That's why a REAL JPA implementation is missing...

Maybe you should reach out to Errai and check if there were good reasons to have these restrictions. My feeling is that a "real jpa" implementation would result in too much overhead from a code size point of view as well as runtime overhead. If a real JPA implementation will cause the browser to hang every now and then if things get a bit more complicated then no one will use it. A browser that feels sluggish because of a library is a no-go.

-- J.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/8k_pqIciRHQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.