[rfc][icedtea-web] add logging to filee for messages from client app

[Jiri Vanek]

Hi!

gain, as hinted in

[rfc][icedtea-web] pre-review - accidental logging tweeking:
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-October/033732.html
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-October/033741.html
and
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-October/033742.html

Here is file log feature for outputs from client app.

As I thought, once log-based logger was removed, [1] no queue was needed.

Whole patch is just refactoring to avoid duplicated code, so the only  actual logic change is:

@@ -155,6 +155,9 @@
          }
          //clients app's messages are reprinted only to console
          if (s.getHeader().isClientApp){
+            if (LogConfig.getLogConfig().isLogToFile()) {
+                getAppFileLog().log(proceedHeader(s));
+            }
              return;
          }
          if (!JNLPRuntime.isDebug() && (s.getHeader().level == Level.MESSAGE_DEBUG

whcih does the whole job.


now there are two questions:

write down  that filelog (+ filelog for clients)  together with log-based filelogger do not work
  xor
implement the second queue which works also with file log
  xor
remove log-based file logger at all.


Second question is how to make new or possible deployment keys visible
  - made checkbox for legacy filelog?
  - made property for logging to file also client content?
    - if so make checkbox for it in itwebsettings?

The best seems to me - property and checbox for  client filelogging with message that it do nto work 
with log based logger, but no checkbox for log-based file log.

  J.

[1] [rfc][icedtea-web] replacing log-based file logger by writer
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-October/033763.html

ps:
diff -r 3553a9b1d152 netx/net/sourceforge/jnlp/runtime/JNLPRuntime.java
--- a/netx/net/sourceforge/jnlp/runtime/JNLPRuntime.java	Fri Oct 16 14:44:31 2015 +0200
+++ b/netx/net/sourceforge/jnlp/runtime/JNLPRuntime.java	Fri Oct 16 15:30:53 2015 +0200
@@ -880,7 +880,11 @@
      }

      public static void exit(int i) {
-        OutputController.getLogger().close();
+        try {
+            OutputController.getLogger().close();
+        } catch (Exception ex) {
+            //to late
+        }
          System.exit(i);
      }


slipped form previous patch [1]. Sorry!