You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two queries running inside ErrorPageHandlerImpl and I believe both can be eliminated.
The first query is to find all the cases where the errorPages property is defined. This can be done without a query by using an InheritanceValueMap to walk up the resource tree from the parent resource.
The second query is to find a page with the appropriate name within the errors path. This can be done by direct node access.
The text was updated successfully, but these errors were encountered:
There are two queries running inside ErrorPageHandlerImpl and I believe both can be eliminated.
The first query is to find all the cases where the errorPages property is defined. This can be done without a query by using an InheritanceValueMap to walk up the resource tree from the parent resource.
The second query is to find a page with the appropriate name within the errors path. This can be done by direct node access.
The text was updated successfully, but these errors were encountered: