}
        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");

        try {
            validator.initialize(annotation);
            assertTrue("Initialize should complete without exception", true);
        } catch (final Exception e) {
            fail("Initialize should not throw exception with valid annotation: " + e.getMessage());
        }
    }

    // Test parameter validation without relying on complex configuration
    @Test
    public void test_validateParameters_basic() {

        assertEquals(originalQueryName, extractedQueryName);
    }

    @Test
    public void test_complex_field_names() {
        // Test various complex field names
        String[] fieldNames = { "simple_field", "field-with-dashes", "field.with.dots", "field_with_underscores", "fieldWithCamelCase",

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

    // Test getRunningJobCount method
    @Test
    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);

- **Flexibility and Control:**
Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully.

- **Security:**
Java serialization poses security risks, especially related to deserialization vulnerabilities.

- **Version Compatibility:**

# 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
    @Test
    public void test_complexSourceMap() {
        TestSearchLogEvent event = new TestSearchLogEvent("complex-id", 1L, "complex");

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

* 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.

        execJob.setExecuteType("crawler");
        assertEquals("prefix-crawler-suffix", execJob.testGetLogName("prefix"));
    }

    // Test complex scenario with multiple configurations
    @Test
    public void test_complexConfiguration() {
        execJob.sessionId("complex-session")
                .logFilePath("/var/log/fess")
                .logLevel("INFO")
                .logSuffix("daily job")

import org.lastaflute.web.validation.ActionValidator;

public class FessActionValidatorTest extends UnitFessTestCase {

    @Test
    public void test_constructor() {
        // Test basic class structure without complex mocking
        assertEquals("FessActionValidator should be in correct package", "org.codelibs.fess.validation.FessActionValidator",
                FessActionValidator.class.getName());
    }

    @Test