fix problem with re-registering superimposing content provider

if a superimposing content provider already exists re-registering failed
because the target properties could not be read from the (already
superimposed) resource. using direkt JCR API access ensures the original
target properties are read from the node.