Code has very little logging about ukwa-ui HOT 2 OPEN

Thanks @bzaar - on 1 and 3, I think this was a mistake on my part. The individual classes we were looking at (we didn't look at them all yet) didn't seem to have much logging, but it seems the most important logging is handled elsewhere.

On 2, I think ideally the classes that Spring configures should report those configured values following initialisation. Just dumping the properties file wouldn't mean anything, because it wouldn't prove they'd been picked up by the code.

from ukwa-ui.

There are cases where exceptions can be swallowed silently. These should probably always log the exceptions unless they really cannot ever happen. One example is the IP filtering code which can hide the fact that system properties may be misformatted.

from ukwa-ui.