I’ve just released a new version of XPages OpenLog Logger.
It’s predominantly a release to catch SSJS errors of classes NotesException and java.io.IOException, as well as wrapping processUncaughtException code in try/catch blocks, to capture any classes I haven’t come across yet. I and other developers have encountered these unexpected error class types when no try/catch has been added to your SSJS code.
One feature has been added. From OpenNTF Domino API I had a request to suppress stack traces from Event logs. Personally I’ve found the stack traces useful on occasion for identifying which lifecycle phase the error first occurs (e.g. Process Validation, Render Response etc.). But if you wish to suppress it for an application or for the server, you can use xsp.openlog.suppressEventStack=true.
Note that all this work has also been done in my branch of OpenNTF Domino API and will be released in due course. If you have deployed OpenNTF Domino API, on its own or as part of OpenNTF Essentials, you don’t need XPages OpenLog Logger. You can just enable the OpenNTF Domino Library for the application instead. If you’ve only used OpenLog via SSJS, there will be no changes. If you’ve used it from Java, OpenLogItem is no longer static, so you will see errors. But the same various logError, logErrorEx and logEvent methods are now available via the XspOpenLogUtil utility class. And if you’ve used any method not in XspOpenLogUtil, you still have XspOpenLogUtil.getOpenLogItem() to get a handle on an OpenLogItem.
Considering that 8.5.3 UP1 has been available for a long time now and has been available as core in Domino 9.0 for nearly a year, this may be the last release that has a non Ext Lib version. The pace of XPages functionality is so significant that 8.5.3 is the earliest server version I would use and I would strongly advise a customer to use Extension Library because of the significant amount of additional functionality available.
