Hey folks,

just a question.
I work at framework which frequently uses KeyValueTuples similar to HashMaps.
The key is a string, the value an Object.
The value could be a KeyValueTuple too, so it comes to an amount of
circular/shared references.


i could handle this by creating every time new instance of TransportMessage and assign the new KeyValueTuple and so on...

My Question is, if there are common ways to handle that ??

Lets make an example.

I had an registry, where i could register and deregister a hibernate class.
A client could search the registry and get some of the registered hibernate objects.

Now, when the client modify and save one of these objects, he shouldn't overwrite the object the registry holds reference to.


possible solutions:

I could set the identifier of the object to null, when the registry give them to the client, whats difficult, because the object has an large object graph.

The client could save an replicate of the object with replicate() , then modify it and then save it in normal way.

Any other suggestions?