Debugging¶
Logging¶
By default, the app server logs at the “INFO” level but logging can be increased to “FINE” on the fly with (for example) ./asadmin set-log-levels edu.harvard.iq.dataverse.api.Datasets=FINE. Running ./asadmin list-log-levels will show the current logging levels.
Java Server Faces (JSF) Configuration Options¶
Some JSF options can be easily changed via MicroProfile Config (using environment variables, system properties, etc.) during development without recompiling. Changing the options will require at least a redeployment, obviously depending how you get these options in. (Variable substitution only happens during deployment and when using system properties or environment variables, you’ll need to pass these into the domain, which usually will require an app server restart.)
Please note that since Payara 5.2021.1 supporting MicroProfile Config 2.0, you can use profiles to maintain your settings more easily for different environments.
JSF Option |
MPCONFIG Key |
Description |
Default |
|---|---|---|---|
javax.faces.PROJECT_STAGE |
dataverse.jsf.project-stage |
Switch to different levels to make JSF more verbose, disable caches etc. Read more at various places. |
|
javax.faces.INTERPRET_EMPTY _STRING_SUBMITTED_VALUES_AS_NULL |
dataverse.jsf.empty-string-null |
|
|
javax.faces.FACELETS_SKIP_COMMENTS |
dataverse.jsf.skip-comments |
|
|
javax.faces.FACELETS_BUFFER_SIZE |
dataverse.jsf.buffer-size |
|
|
javax.faces.FACELETS_REFRESH_PERIOD |
dataverse.jsf.refresh-period |
|
|
primefaces.THEME |
dataverse.jsf.primefaces.theme |
|
Previous: Writing Documentation | Next: Coding Style