Skip to content

Latest commit

 

History

History
42 lines (26 loc) · 2.73 KB

README.md

File metadata and controls

42 lines (26 loc) · 2.73 KB
Raw

IMPORTANT

The XPages Debug Toolbar has been packaged as a plugin and is now maintained in the OpenNTF repository on GitHub (http://www.github.com/openntf/debugtoolbar).

What's new in version 3 of the XPage Debug Toolbar

  • New feature: external logging

    • Stores messages written to the toolbar in documents in a database, (optional) including messages thrown by the XPages runtime in an error page.
    • Settings managed through dBar bean managed bean properties: logDbPath current or logs\logdb.nsf logEnabled true/ false (defaults to false) logLevel error, warn, info, debug determines message types that are logged, will include all previous log types
    • All users that need to be able to log something to the log databse need to have (at least) depositor access. If they also need to be able to read log documents, give them Author access with the Create documents option.

  • New feature: read server log files

  • New options in Messages tab: detailed timings

    • shows milliseconds for every log message

  • Redesigned "Inspector":

    • removed debug toolbar components from component selection list
    • executing a statement now does a full refresh, so you can instantly see the effect (try a button.setDisabled(true) for instance!)
    • changed sort order for component ids: ids starting with a _ moved done
    • layout changes: click on methods to execute them, classes to open the documentation site
    • goto previous expression

  • Layout changes

    • simplified CSS (i.e. CSS3 selectors for zebra tables)
    • better compatibility with Bootstrap/ JQM

  • Removed "Timers" tab

    • startTimer() en stopTimer() are now deprecated (replaced by debug() calls)

The dBar managed bean property "enabled" has been renamed to "toolbarVisible" and defaults to false. Normally you don't need to use this property: it is automatically set when the toolbar is rendered in a browser. This is done so you can leave all dBar.someFunction() calls intact when moving an applicationn to production. If the toolbarVisible property remains false, the calls won't do anything (and thus have no negative impact on your application's performance). The toolbarVisible property works independant from any configured external logging database, so you can still have external logging of (for instance) only warnings and errors without showing the toolbar at all (or only showing it to users with the [debug] role).

There's 1 downside to this: the toolbarVisible property is automatically set to true in the ccDebugToolbar's beforPageLoad event (since the toolbar is loaded) so any dBar.XXX calls in the calling XPages's beforePageLoad event won't have an effect. To change this behaviour, you can set the property as a managed property in the dBar bean configuration.