// ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private WebConfigService webConfigService;
    @Resource
    private ScheduledJobService scheduledJobService;

            public long getLastWriteTime() { return fileInfo.getLastModified(); }
            @Override
            public boolean isDirectory() { return fileInfo.isDirectory(); }
            // ... other attribute methods
        });
        
        return file;
    }
}
```

### 4.4 Directory Change Notifier
```java
package jcifs.internal.smb2.lease;

import jcifs.internal.smb2.ServerMessageBlock2;

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** Service for file authentication operations. */
    @Resource
    private FileAuthenticationService fileAuthenticationService;

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private RequestHeaderService requestHeaderService;
    @Resource
    private ReqHeaderPager reqHeaderPager;

Der Grund ist, dass das das generierte JSON-Schema in der OpenAPI Ihrer Anwendung (und deren Dokumentation) dennoch das komplette Modell abbildet, selbst wenn Sie `response_model_include` oder `response_model_exclude` verwenden, um einige Attribute auszuschließen.

Das trifft auch auf `response_model_by_alias` zu, welches ähnlich funktioniert.

///

{* ../../docs_src/response_model/tutorial005_py310.py hl[29,35] *}

/// tip | Tipp

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========

    // ===================================================================================

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** Service for label type operations. */
    @Resource
    private LabelTypeService labelTypeService;

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private CharMappingService charMappingService;
    @Resource
    private CharMappingPager charMappingPager;

// we assume the value returned by the LDAP server is canonical. Additionally,
// the attribute type names in the DN are lower-cased.
//
// Return values:
//
// If the DN is found, the normalized (string) value and any requested
// attributes are returned and error is nil.
//
// If the DN is not found, a nil result and error are returned.
//

        </field>
        <field>
          <name>organization</name>
          <version>3.0.0+</version>
          <description>This element describes various attributes of the organization to which the
            project belongs. These attributes are utilized when documentation is created (for
            copyright notices and links).</description>
          <alias>organisation</alias>
          <association>