Consider this use case: I have an inventory transaction that transfers goods from one warehouse to another. I need to increase inventory in receiving location and decrease inventory in issuing location. Each location has a stock ledger entity. I want the increase in receiving stock ledger entity quantityAtHand and the decrease in the issuing stock ledger entity quantityAtHand to be handled as one transaction ie succeed or fail together. And this happens programmatically as part of the lifecycle of the transaction entity.
Sent from my iPad On Jul 20, 2013, at 10:07 PM, David Tildesley <[email protected]> wrote: > Hi O. would be easier to answer your question if you described your use > case. If it is just single database persistence I would question why you > would want to do this in the first place. But anyway, I don't see any reason > why you couldn't detach your business objects using jdo detachable, work on > them, and when you are ready to save, call your custom operation to reattach > and persist (the viewer will do the transaction).. > > But I'm not a developer, I'm an architect so you will need some further > advice on this. > > David. > > Sent from Yahoo! Mail on Android >
