have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.user.User" />

        assertTrue(confPath.toString().contains("file.conf"));
    }

    public void test_getConfOrClassesPath() {
        // Test behavior when resource is not found
        try {
            Path path = ResourceUtil.getConfOrClassesPath("nonexistent.conf");
            fail("Should throw ResourceNotFoundRuntimeException for non-existent file");
        } catch (org.codelibs.core.exception.ResourceNotFoundRuntimeException e) {

# Body – Mehrere Parameter

Jetzt, da wir gesehen haben, wie `Path` und `Query` verwendet werden, schauen wir uns fortgeschrittenere Verwendungsmöglichkeiten von Requestbody-Deklarationen an.

## `Path`-, `Query`- und Body-Parameter vermischen

Zuerst einmal, Sie können `Path`-, `Query`- und Requestbody-Parameter-Deklarationen frei mischen und **FastAPI** wird wissen, was zu tun ist.

/**
 * Provides classes for managing Maven toolchains, which allow projects to use specific
 * tool installations (like JDKs, compilers, or other build tools) across different
 * environments without hardcoding paths.
 *
 * @since 4.0.0
 */

    @Test
    @DisplayName("Test multiple path operations")
    void testMultiplePathOperations() {
        request = new Smb2CreateRequest(mockConfig, "initial\\path.txt");
        assertEquals("\\initial\\path.txt", request.getPath());

        request.setPath("\\second\\path.txt");
        assertEquals("\\second\\path.txt", request.getPath());

        request.setPath("third\\path\\");

public final class UnixDomainSocketFactory extends SocketFactory {
  private final File path;

  public UnixDomainSocketFactory(File path) {
    this.path = path;
  }

  @Override public Socket createSocket() throws IOException {
    UnixSocketChannel channel = UnixSocketChannel.open();
    return new TunnelingUnixSocket(path, channel);
  }

  @Override public Socket createSocket(String host, int port) throws IOException {

package jcifs.smb1.smb1;

import jcifs.smb1.util.Hexdump;

class SmbComDelete extends ServerMessageBlock {

    private final int searchAttributes;

    SmbComDelete(final String fileName) {
        this.path = fileName;
        command = SMB_COM_DELETE;
        searchAttributes = ATTR_HIDDEN | ATTR_HIDDEN | ATTR_SYSTEM;
    }

    @Override
    int writeParameterWordsWireFormat(final byte[] dst, final int dstIndex) {

        assertEquals("http://192.168.1.1/path/file", HcHttpClient.constructRedirectLocation("http://192.168.1.1/path/", "file"));
        assertEquals("http://[2001:db8::1]/path/file", HcHttpClient.constructRedirectLocation("http://[2001:db8::1]/path/", "file"));
        assertEquals("http://example.com:8080/path/file", HcHttpClient.constructRedirectLocation("http://example.com:8080/path/", "file"));

`Field`는 `Query`, `Path`와 `Body`와 같은 방식으로 동작하며, 모두 같은 매개변수들 등을 가집니다.

/// note | 기술적 세부사항

실제로 `Query`, `Path`등, 여러분이 앞으로 볼 다른 것들은 공통 클래스인 `Param` 클래스의 서브클래스 객체를 만드는데, 그 자체로 Pydantic의 `FieldInfo` 클래스의 서브클래스입니다.

그리고 Pydantic의 `Field` 또한 `FieldInfo`의 인스턴스를 반환합니다.

`Body` 또한 `FieldInfo`의 서브클래스 객체를 직접적으로 반환합니다. 그리고 `Body` 클래스의 서브클래스인 것들도 여러분이 나중에 보게될 것입니다.

    constructed = false // The enclosed object written in block() is not constructed.
    path += name
    try {
      block(content)
      constructedBit = if (constructed) 0b0010_0000 else 0
      constructed = true // The enclosing object is constructed.
    } finally {
      stack.removeAt(stack.size - 1)
      path.removeAt(path.size - 1)
    }

    val sink = sink()