spacemanager,transfermanagers: Don't rely on SRM db properties

Several service have historically piggybacked on the SRM db
settings. Nowadays each service has its own DB properties, however
spacemanager and transfermanagers defines it's properties in
terms of the SRM properties, thus causing an unwanted coupling.

We still want backwards compatibility and thus let spacemanager
and transfermanagers default to the deprecated (legacy) srm
properties, however the new properties should be decoupled. This
structure matches what is already done in pinmanager.

At the same time, both spacemanager and transfermanagers did
not actually respect it's own properties: That's because they
used the JDBC URL defined for the SRM and these didn't make
use of properties like spacemanager.db.host and spacemanager.db.name.

Target: trunk
Require-notes: yes
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5901/
srm: Drop properties marked obsolete or forbidden in 2.6

We cannot keep them forever and for other services we dropped
old properties in 2.7.

Target: trunk
Require-notes: yes
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5902/
pnfsmanager: Use pnfsmanager.enable.* for properties that enable features

Changes

pnfsmanager.folding -> pnfsmanager.enable.folding
pnfsmanager.inherit-file-ownership -> pnfsmanager.enable.inherit-file-ownership
pnfsmanager.full-path-permission-check -> pnfsmanager.enable.full-path-permission-check
pnfsmanager.acl -> pnfsmanager.enable.acl

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5903/
SRM: fix ping

SRM includes code that checks if a reponse is successful.  It does
this by invoking the getReturnStatus that Axis creates, via
reflection.

Unfortunately, not all response objects contain this method (the
response from a ping operation is the only example).  The current
code that evaluates whether a response is successful results in a
NoSuchMethodException being thrown for such operations.  This
exception is treated as a failure, resulting in ping no longer
working.

This patch fixes this problem by catching the NoSuchMethodException
and treating such operations as always succeeding.  (Catching the
exception like this is not nice, but seems the least ugly way of
discovering if the response object contains the desired method).

Target: master
Requires-notes: no
Requires-book: no
Patch: http://rb.dcache.org/r/5904/
Acked-by: Gerd Behrmann