@Override
  protected void setUp() throws Exception {
    super.setUp();

    handler = new TestLogHandler();

    // You could also apply it higher up the Logger hierarchy than this
    ExampleClassUnderTest.logger.addHandler(handler);

    ExampleClassUnderTest.logger.setUseParentHandlers(false); // optional

    stack.addTearDown(
        () -> {

  @Override
  protected void setUp() throws Exception {
    super.setUp();

    handler = new TestLogHandler();

    // You could also apply it higher up the Logger hierarchy than this
    ExampleClassUnderTest.logger.addHandler(handler);

    ExampleClassUnderTest.logger.setUseParentHandlers(false); // optional

    stack.addTearDown(
        () -> {

        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());
    }

    @Test
    public void test_instanceOf() {
        // Test inheritance hierarchy
        UnsupportedSearchException exception = new UnsupportedSearchException("test");

        assertTrue(exception instanceof UnsupportedSearchException);
        assertTrue(exception instanceof FessSystemException);

        // Setup
        final String message = "Test inheritance hierarchy";
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsInvalidQueryUnknown(UserMessages.GLOBAL_PROPERTY_KEY);

        // Execute
        final InvalidQueryException exception = new InvalidQueryException(messageCode, message);

        // Verify inheritance hierarchy
        assertTrue(exception instanceof FessSystemException);

src/main/webapp/WEB-INF/view/  # JSP templates
src/test/java/.../it/          # Integration tests (*Tests.java)
```

## Architecture Patterns

### Action (Controller)
- Hierarchy: `TypicalAction` → `FessBaseAction` → `FessAdminAction`/`FessSearchAction`
- `@Execute` marks web endpoints
- `@Resource` for DI
- `@Secured({ "role", "role-view" })` for authorization

The simpler the problem solved by the tool, the better performance it will get. And most of the benchmarks don't test the additional features provided by the tool.

The hierarchy is like:

* **Uvicorn**: an ASGI server
    * **Starlette**: (uses Uvicorn) a web microframework

- `crawler/filter.xml`, `crawler/interval.xml`, `crawler/contentlength.xml`, `crawler/urlconverter.xml`, `crawler/container.xml`, `crawler/log.xml`

### Exception Hierarchy

All exceptions are unchecked (extend `RuntimeException` via `CrawlerSystemException`).

```
CrawlerSystemException (RuntimeException)
  ├─ CrawlingAccessException
  │     └─ MaxLengthExceededException

                break;
            }
        }
        assertTrue(foundTestMethod);
    }

    @Test
    public void test_inheritanceHierarchy() {
        // Test inheritance hierarchy
        SearchQueryException exception = new SearchQueryException("Inheritance test");

        assertTrue(exception instanceof SearchQueryException);
        assertTrue(exception instanceof FessSystemException);

                hasCronExpression = true;
                break;
            }
        }
        assertTrue(hasCronExpression);
    }

    // Test class hierarchy validation
    @Test
    public void test_inheritanceValidation() {
        ExtendedTestBean bean = new ExtendedTestBean();
        bean.setCronExpression("invalid");
        bean.setAdditionalCron("also invalid");

* Even dependencies can have dependencies, creating a hierarchy or **"graph" of dependencies**.
* All **automatically handled** by the framework.
* All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.