Am 08.10.14 um 21:36 schrieb Sandro Boehme: > It doesn't work as the wrapper uses the original resource metadata object. > I could create a wrapper for the resource metadata as well and remove > the lock check. This way I would need to dublicate all resource metadata > methods in the resource metadata wrapper for the delegation. But every > signature change in the evolution of the ResourceMetadata class would > have to be synchronized with its wrapper. This seems to be a very tight > dependency. Is this really the way to go? >
Usually you create a new metadata object for the resource wrapper. I see that maybe our wrapper implementation should do this by default. So I think, the right way is to create a new metadata object for the wrapper and copy the metadata you want to keep from the original resource. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
