abandom use of boolean result values and JUL messages - instead propogate exceptions up the stack
abandom use of boolean result values and JUL messages - instead propogate exceptions up the stack

experimenting showed that even in apps where SLF4J was used in the boot loader to override the log framework, messages were still coming direct from JUL, so i switched to using simple System.err.println in demo mode, and eliminated other log messages in favor of wrapping an re-throwing exceptions

LucidWorks/mlockall-agent