-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ViewExpiredException when rendering error.xhtml #4838
Comments
Update: It looks like this error only occurs if another error has previously occurred during page load (an instance of #3762 in my case). Removing the call to |
@matthias-ronge Omniface can ignore ViewExpiredException in web.xml. Another possible solution is to optimize log4j2 logger to log other packages than "org.kitodo". There are existing logger configs for src and test in every module #4849. So we should consolidate this to one logger, cause insufficient logger config in some cases swallow exceptions. |
@matthias-ronge JSF swallows exceptions when value of PROJECT_STATE is not "Development". I added following in web.xml but that should only be available for developer purposes. Besides that it's recommended to extend the FACELETS_BUFFER_SIZE.
After that Nullpointer exceptions will be displayed. |
…ect stage on development
…o_kitodo_module #4838 add development profile to kitodo which puts the jsf project st…
I encounter ViewExpiredException when opening a process in the metadata editor. Stack trace is:
I could find out that this happens when resolving the following expression:
#{SessionClientController.currentSessionClientName}
for which I found only one occurrence, innavigation.xml
, line 109.In
UserService.getCurrentUser(UserService.java:225)
:getAuthenticatedUser()
returnsnull
fromSecurityAccess.getCurrentAuthentication(SecurityAccess.java:139)
:because the security context it picks up doesn’t contain an authentication. The field
authentication
inside it isnull
in the debugger, which is returned.This happens when I am logged in, and there are subsequent calls to these functions when the page is built, which correctly return the authenticated user.
The text was updated successfully, but these errors were encountered: