The purpose of the PM class is to abstract the PersistenceManager away from
my logic. Because the datastore doesn't allow unowned relationships, my
business logic which is located in the Persisted objects, must retrieve the
objects to perform there tasks. The PM object allows me to write Unit Tes
The PM class may be an over-optimization. Can you help me understand what
the purpose of this class is? There shouldn't be any significant costs
associated with opening, closing and retrieving instances of
PersistenceManager.
On Tue, Nov 24, 2009 at 10:34 AM, Jeffrey Goetsch wrote:
> Here is a su
Here is a subset of the code. It doesn't run or have the logic that changes
the values. I have included the ChallengeDao, which highlights what I had
to do to make work correctly. If I remove the PM.closePersistentManager()
it fails in many different ways. I can even get a failure about can't
m
Can you post a subset of your code? It'd be great for the community to take
a look at what you are doing and see if there's anything that jumps out at
us.
On Sat, Nov 21, 2009 at 11:46 PM, Jeffrey Goetsch wrote:
> I have been having a lot of trouble with JDO objects not storing, or at
> least not
I have been having a lot of trouble with JDO objects not storing, or at
least not storing some of the data. This has been extremely frustrating,
and have thought about giving up on Appengine a few times, because my
current design seems bring out all the bugs in the Datastore/Datanucleus
code. Are
