Details
-
Improvement
-
Resolution: Fixed
-
Major
-
3.5.4
-
None
Description
The exceptions were all being caught and logged in the QueryUtil - and therefore were unavailable for the JCR Utils page to get them to display.
I made another "exceptionThrowingQuery" method in the QueryUtil that throws exceptions, and called that method in the JCR Utils method. To avoid duplicate code, the query method now delegates the actual query to the exceptionThrowingQuery method and the traps the exception, logs it, and returns the Collections.EmptyList (identical behavior to what it was before)
In addition, the size of the collection returned is now printed when results are returned. This can be helpful for knowing row counts... etc.
Checklists
Attachments
Issue Links
- is related to
-
MAGNOLIA-1396 Workflow module api/code cleanup
-
- Closed
-
- supersedes
-
MAGNOLIA-1338 Query utility silently ignores invalid queries
-
- Closed
-