QuoteReplyTopic: Should I use a single PersistenceManager or many? Posted: 12-Jul-2007 at 4:40pm
Actually, you have three choices
One PM
Multiple PM’s
A hybrid approach
I would advise you to start with just a single PM.This is certainly the easiest approach.It is also the most consistent approach in that each form represents the same view of any particular business object as any other form.
Consider multiple PM’s if you want any additions, deletions, or changes in one form not to be present in any other form until you save the first form.In addition, you can do an Undo on one form independent of the state of another,The disadvantage of using multiple PM’s is that managing them can be complex.Moving changes from one PM can be tricky (for example, you’ll have to deal with possible concurrency conflicts).
Finally, there is the hybrid approach.View the TechTip which uses theGetEntityGraph at
Now that I have confused you, I would strongly recommend that you start with a single PM.If after you have success with this approach, you might look at other alternatives.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum