Since the naming of the properties no longer suggests they are experimental, we want to ensure users are aware if the current property stops having an effect.
Since the underlying feature is incubating, its actual behavior can still change or be removed in the minor releases.

These properties CAN be supplemented with command-line options and they SHOULD follow the shared naming scheme described above.

        // Test the specific field naming configuration
        JsonMappingOption option = provider.provideMappingOption();

        // The option should be configured with CAMEL_TO_LOWER_SNAKE
        // Field naming is now provided as OptionalThing
        OptionalThing<JsonFieldNaming> fieldNamingOpt = option.getFieldNaming();
        assertTrue("Field naming should be present", fieldNamingOpt.isPresent());

├── lang/        # Reflection & language utilities
├── log/         # Logging utilities
├── message/     # Message resource handling
├── misc/        # AssertionUtil, Base64Util, etc.
├── naming/      # JNDI naming utilities
├── net/         # Network & URL utilities
├── nio/         # NIO file utilities
├── security/    # Security & MessageDigest utilities
├── sql/         # SQL type utilities

- **Strategy**: Normalizer, ReadingConverter, ContentsParser
- **Deferred/Promise**: Async operations

### Index Alias Strategy

Zero-downtime index updates using dual aliases:

```
Index Naming: {baseIndex}.{timestamp}
Example:      my-suggest.20250123120000

Aliases:
├── Search Alias: {baseIndex}          (read operations)
└── Update Alias: {baseIndex}.update   (write operations)
```

        // Create custom naming convention
        NamingConvention customNamingConvention = new MockNamingConvention() {
            @Override
            public String fromClassNameToComponentName(String className) {
                return super.fromClassNameToComponentName(className);
            }
        };

        // Create PagerCreator with custom naming convention

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

- Authentication: Local (UserService), LDAP, OIDC, SAML, SPNEGO, Entra ID
- Security features: AES encryption, SHA256 digest, LDAP injection prevention, password policy, rate limiting

## Naming Conventions

| Element | Convention | Example |
|---------|------------|---------|
| Classes | PascalCase | `UserService`, `FessBaseAction` |
| Methods | camelCase + verb | `getUserList()`, `setupHtmlData()` |

In limited situations OkHttp will retry a route if connecting fails:

 * When making an HTTPS connection through an HTTP proxy, the proxy may issue an authentication challenge. OkHttp will call the proxy [authenticator](https://square.github.io/okhttp/5.x/okhttp/okhttp3/-authenticator/) and try again.

                }
            }
        }
        assertTrue("Should have unique paths", paths.size() > 0);
    }

    @Test
    public void test_pathNamingConvention() throws Exception {
        // Test field naming follows convention
        Field[] fields = FessHtmlPath.class.getDeclaredFields();
        for (Field field : fields) {
            int modifiers = field.getModifiers();

 * </ul>
 */
@SuppressWarnings({
  // We call threadUnexpectedException, which does the right thing for errors.
  "AssertionFailureIgnored",
  // We're following the upstream naming to reduce diffs.
  "IdentifierName",
  "ConstantCaseForConstants",
})
@NullUnmarked
@GwtIncompatible
@J2ktIncompatible
abstract class JSR166TestCase extends TestCase {