} catch (final Exception e) {
            fail("Initialize should not throw exception with valid annotation: " + e.getMessage());
        }
    }

    // Test parameter validation without relying on complex configuration
    public void test_validateParameters_basic() {
        // Test that parameter validation can be performed
        final CustomSize validAnnotation = createBasicAnnotation();

        try {

        }
        searchRenderData.setDocumentItems(documents);

        searchRenderData.setSearchQuery("complex search query");
        searchRenderData.setQueryTime(150L);
        searchRenderData.setExecTime("0.15 sec");
        searchRenderData.setRequestedTime(System.currentTimeMillis());
        searchRenderData.setQueryId("complex-query-id");
        searchRenderData.setAppendHighlightParams("&hl=true&hl.fl=title,content");

        assertTrue(result.contains("Data Config Id: data1"));
    }

    // Test getRunningJobCount method
    public void test_getRunningJobCount() {
        // Skip this test - requires complex DB setup
        if (true)
            return;
        // Setup test with mock ScheduledJobBhv
        final AtomicInteger callCount = new AtomicInteger(0);

It is quite an extensive specification and covers several complex use cases.

It includes ways to authenticate using a "third party".

That's what all the systems with "login with Facebook, Google, X (Twitter), GitHub" use underneath.

### OAuth 1 { #oauth-1 }

There was an OAuth 1, which is very different from OAuth2, and more complex, as it included direct specifications on how to encrypt the communication.

                WebResourceRoot.class.isAssignableFrom(FessWebResourceRoot.class));
    }

    public void test_classStructure() {
        // Basic class structure tests that don't require complex mocking
        assertEquals("FessWebResourceRoot should be in correct package", "org.codelibs.fess.tomcat.webresources.FessWebResourceRoot",
                FessWebResourceRoot.class.getName());

# Extra Data Types { #extra-data-types }

Up to now, you have been using common data types, like:

* `int`
* `float`
* `str`
* `bool`

But you can also use more complex data types.

And you will still have the same features as seen up to now:

* Great editor support.
* Data conversion from incoming requests.
* Data conversion for response data.
* Data validation.
* Automatic annotation and documentation.

            // Just verify the methods are callable
            assertTrue(true);
        }
    }

    // Test with complex source map
    public void test_complexSourceMap() {
        TestSearchLogEvent event = new TestSearchLogEvent("complex-id", 1L, "complex");

        // Create nested map structure
        Map<String, Object> nestedMap = new HashMap<>();

        assertNull(result.getDocumentList().get(0));
    }

    public void test_complexDocumentStructure() {
        // Test with complex nested document structure
        Map<String, Object> doc = new HashMap<>();
        doc.put("id", "complex");

        Map<String, Object> nested = new HashMap<>();
        nested.put("level2", "value");
        doc.put("nested", nested);

* Validate **complex structures**:
    * Use of hierarchical Pydantic models, Python `typing`’s `List` and `Dict`, etc.
    * And validators allow complex data schemas to be clearly and easily defined, checked and documented as JSON Schema.

        assertNotNull(result);
        assertEquals(-1, ((QueryRescorerBuilder) result).windowSize().intValue());
    }

    public void test_evaluate_withComplexParams() {
        // Test with complex parameter map including nested structures
        final String testModelName = "complex_model";
        final int testWindowSize = 200;

        ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {