Did we really mean the new deep copy or the materialize sub objects function? My work on 13088 was to materialize sub objects (presumably so they could be copied)

I'm checking into the usage of the methods I did replace throughout the Rice code to see what I can adjust. I'm also able to update the KRAD LDA so that it will call the new code.

I'm working on replacing those methods. The replacements seem to work without introducing any problems to BO copy on KRAD and KNS screens.

Now - there does not seem to be any use of the ObjectUtils.deepCopy() methods within non-KNS components of Rice. So, I don't see anything to change with regards to those.

Pretty much we need to be able to replace the hacks we put in with your new method so we don't have to keep having to patch this. It could be very well that "deep copy" is the wrong terminology.

OK - found what I need to research here.

Because of the way that JPA works - we can not use serialization as a method of duplicating our objects for copies. The code in ContextBo is using:

org.kuali.rice.core.api.util.io.SerializationUtils.deepCopy()

Code which needs to copy a persisted object will need to be updated to use

DataObjectService.copyInstance()

Though - from some discussions with Martin - there may be more we need to do in that copyInstance method to make this work correctly. (It seems that some "residue" may get left behind that we need to clean up.)