> btw why does em.flush() throw an exception declaring that it requires > a transaction and that there is none in context when the Persistence > Provider is clearly configured for non-tx writes
You mean according to the JPA spec 3.1.1, for flush() <spec> @throws TransactionRequiredException if there is no transaction </spec> so it complies with the JPA TCK then. Don't call flush in a non-tx context. --Andy (DataNucleus) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
