* {@code jcifs.smb.client.domain} or {@code jcifs.http.domainController}
 * properties are be specified. <b>With later containers the
 * {@code NtlmHttpFilter} should be used</b>. For custom NTLM HTTP Authentication schemes the {@code NtlmSsp} may be
 * used.
 * <p>
 * Read <a href="../../../ntlmhttpauth.html">jCIFS NTLM HTTP Authentication and the Network Explorer Servlet</a> related
 * information.
 *

 * plugins should always acquire model builder instances via dependency injection. Developers might want to subclass
 * this factory to provide custom implementations for some of the components used by the model builder.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public class DefaultModelBuilderFactory {

 * lifecycle phase. Standard lifecycles use plugin execution {@code <phase>} or mojo default lifecycle phase to
 * calculate the execution plan, but custom lifecycles can use alternative mapping strategies.
 */
@Named(DefaultLifecycleMappingDelegate.HINT)
@Singleton
public class DefaultLifecycleMappingDelegate implements LifecycleMappingDelegate {

<img src="/img/tutorial/additional-responses/image01.png">

## Ön Tanımlı Response'ları Özel Olanlarla Birleştirme { #combine-predefined-responses-and-custom-ones }

Birçok *path operation* için geçerli olacak bazı ön tanımlı response'larınız olabilir; ancak bunları her *path operation*'ın ihtiyaç duyduğu özel response'larla birleştirmek isteyebilirsiniz.

    }

    @Test
    void constructor_withAllParameters_shouldInitializeCorrectly() {
        Name name = new Name(mockConfig, "TestName", 0x20, "custom.scope");

        assertEquals("TESTNAME", name.name);
        assertEquals(0x20, name.hexCode);
        assertEquals("custom.scope", name.scope);
        assertEquals(0, name.srcHashCode);
    }

    @Test
    void constructor_withLongName_shouldTruncateTo15Characters() {

    - [**API Machinery**](#api-machinery-3)
      - [**Admission Control**](#admission-control)
      - [**API & API server**](#api-&-api-server)
      - [**Audit**](#audit)
      - [**Custom Resources**](#custom-resources)
      - [**Other**](#other)
    - [**Apps**](#apps-1)
    - [**Auth**](#auth-3)
      - [**Audit**](#audit-1)
      - [**RBAC**](#rbac)
      - [**Other**](#other-1)
      - [**GCE**](#gce)

    }

    @Test
    public void test_getMessage() {
        // Test getMessage() method
        String message = "Custom SSO error message";
        SsoLoginException exception = new SsoLoginException(message);

        assertEquals(message, exception.getMessage());

        // Test with special characters

        LeaseEntry entry = leaseManager.getLease(key);
        assertNotNull(entry);
        assertEquals(newState, entry.getLeaseState());
    }

    @Test
    @DisplayName("Should clean up expired leases with custom timeout")
    void testCleanupExpiredLeasesWithCustomTimeout() throws InterruptedException {
        String path1 = "/share/expired1.txt";
        String path2 = "/share/expired2.txt";

이 모든 내용은 OpenAPI에 결합되어 포함되고, API 문서에 표시됩니다:

<img src="/img/tutorial/additional-responses/image01.png">

## 미리 정의된 응답과 커스텀 응답 결합하기 { #combine-predefined-responses-and-custom-ones }

여러 *경로 처리*에 적용되는 미리 정의된 응답이 필요할 수도 있지만, 각 *경로 처리*마다 필요한 커스텀 응답과 결합하고 싶을 수도 있습니다.

그런 경우 Python의 `dict` “unpacking” 기법인 `**dict_to_unpack`을 사용할 수 있습니다:

```Python
old_dict = {

所有这些都会被合并并包含到你的 OpenAPI 中，并显示在 API 文档里：

<img src="/img/tutorial/additional-responses/image01.png">

## 组合预定义响应和自定义响应 { #combine-predefined-responses-and-custom-ones }

你可能希望有一些适用于许多*路径操作*的预定义响应，但同时又想把它们与每个*路径操作*所需的自定义响应组合在一起。

在这些情况下，你可以使用 Python 的“解包”`dict` 的技巧 `**dict_to_unpack`：

```Python
old_dict = {
    "old key": "old value",