Detach/makePersistence DTO behaviour

Question

Suppose I have a DAO with crud methods and it handles DTOs which are detached instances of persistence capable classes, for instance:
//DAO
public void update(MyDto dto)
   pm.makePersistent(dto)
//APP
MyDto detachedDto = ...
myDao.update(detachedDto);The dto passed in gets attached using makePersistent but does the client's instance of detachedDto suddenly become persistent?
I was reading the javadocs for PersistenceManager.makePersistent:
"Any references to the detached instances from instances in the closure of the parameter instances are modified to refer to the corresponding persistent instance instead of to the detached instance."
I get lost somewhere in the middle of the that sentence. Can anyone shed some light on the behaviour in this case?
Thanks.
Mark

Answer 1

Is there a particular reason you did not make all classes detachable (it
changes enhancement only slightly and in a non-interfering way). If you
want to trim the object graph, you would be better served using fetch
groups.
Den Orlov wrote:
Guys!
We are trying to use 'detach-on-close' option of PersitanceManager. But we
have only some small subset of PersitentCapable objects that are stored in
HTTPSession. So we decided to mark only this subset as 'detachable'.
And... have got kodo.util.UserException that in fact tales us that we
should mark ALL PersitentCapable managed by PersitanceManager as
'detachable'. Oops!
Is there any way to use 'detach-on-close' only with concrete subset of
PersitentCapable objects? It's very strange that PersistentManager uses
detachAll() method instead of checking detachable metadata of its managed
PersitentCapable objects.
Thanks in advance for any help or info by the subject,
Den Orlov
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com