> it either saves or silently does nothing. I would like to know if there are > any patterns for:
Define "does nothing". The log tells what it does. Why not post it here for the operation in question ... > 1) Creating / closing the PersistenceManager: Should i reuse the > PersistenceManager for the whole request? Can i use ThreadLocal to > make it available for the request? A typical pattern for a web-tier is PM per request. Creation of PM is not expensive either FWIW > 2) What influences the JDO? Can i use as many nested objects, methods > (instance and static), try catches, as my design wishes? JDO imposes very little on your code (doesnt persist static/final fields but thats all), aka transparent persistence > 3) Is JDO "usable" at all? Or should i go low-level ? JDO is obviously usable since there are articles by people using it, and articles by Google on their blog about how to handle particular features. Depending on what you're doing governs which API you use. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
