Hi Thomas! Actually, I think both erros should fire on page loading, before any request. The ui:include is used to separate the content of the dialog from the main page, so the stack trace of errors on the dialog could be shown on loading the main page.
For the record, by setting ERROR_HANDLING to false, the stack trace is correctly written to the server log, for both cases, on page loading. Em ter., 7 de jan. de 2025, 07:12, Thomas Andraschko < [email protected]> escreveu: > both are non-ajax requests? > > Am Di., 7. Jan. 2025 um 01:48 Uhr schrieb Fernando Mattioli < > [email protected]>: > > > Hi! > > > > Setting up the Open Liberty dev plugin for an existing project, I came > > across the following issue: having the org.apache.myfaces.ERROR_HANDLING > > context parameter set to true, errors on main facelets (for example, > typos > > on properties names) are correctly handled, and the corresponding stack > > trace is presented. However, when this same kind of error occurs inside a > > primefaces dialog, stack trace is not shown (neither valuable log > > information, on the server log). > > > > Is there any way I can get this stack trace on screen, as in the first > > scenario? If it helps, I've setup this > > < > > > https://github.com/f-matt/open-liberty-examples/tree/main/primefaces-dialog > > > > > sample project. For example, by changing the bean properties with > > non-existing ones (indexView.message -> indexView.wrongMessage and > > indexView.dialogMessage -> indexView.wrongDialogMessage), one should view > > the stack trace for index.xhtml, but not for dialog.xhtml. > > > > Finally, if this is not a MyFaces issue, please let me know so I can > report > > it on the Open Liberty or Primefaces lists. > > > > Many thanks in advance. Best regards! > > > > > > -- > > Fernando Mattioli > > >
