#10 Compatability: beta breaks application logging

[James Stiefel]

Prior to 1.2.1 beta, ozone applications server-side
logging was lumped in together with ozone server log
lia log4j, controlled by ozone logging.properties.
Since core has switched to Java logging, all exisitng
applications have been orphaned. Existing applications'
log messages are entirely igonred when run under the
beta, and there is no facility (such as an application
context) by which an application can configure log4j.

While migrating all apps to Java logging may be
acceptable in the long term, there is currently no
transition path to that end.

We need to re-enabel log4j. Even if ozone does not use
it, the server needs to configure the log4j system on
behalf of all old applications (as it did before) so
they can continue to generate log messages.