In versions prior to gvSIG 2.0, a common practice when implementing object cloning was to use persistence. An object was persisted and then 'unpersisted' to obtain a copy.

However, in gvSIG 2.0 this method will probably not work, as the new persistence API takes control of object references to avoid duplicating objects already loaded on the system, and so you may not get the desired results.

To implement object cloning a new API has been defined in *org.gvsig.tools*, as well as a `development guide`__ that shows how to implement and use cloning.

__ https://gvsig.org/web/reference_catalog/lookupObject?uuid=7becef66ca0d08741666d140fc459b4a