* Contains the relative ID and name of a SAM object.
     */
    public static class SamrSamEntry extends NdrObject {

        /**
         * Default constructor for SamrSamEntry.
         */
        public SamrSamEntry() {
            // Default constructor
        }

        /** The relative ID (RID) of the SAM entry */
        public int idx;

     * Contains the relative ID and name of a SAM object.
     */
    public static class SamrSamEntry extends NdrObject {

        /**
         * Default constructor for SamrSamEntry.
         */
        public SamrSamEntry() {
            // Default constructor
        }

        /** The relative ID (RID) of the SAM entry */
        public int idx;

    }

    @Test
    @DisplayName("parseURL: relative spec without scheme is prefixed for empty host")
    void testParseURL_RelativeSpecWithEmptyHost() throws MalformedURLException {
        // Arrange: base URL with empty host
        Handler handler = newHandler();
        URL base = new URL(null, "smb://", handler);

        // Act: relative path should exercise the 'else if' path in parseURL

Así que usamos un import relativo con `..` para las dependencias:

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[3] title["app/routers/items.py"] *}

#### Cómo funcionan los imports relativos { #how-relative-imports-work }

/// tip | Consejo

import java.util.Arrays;
import java.util.Comparator;
import java.util.Iterator;
import java.util.List;
import org.jspecify.annotations.Nullable;

/**
 * An accumulator that selects the "top" {@code k} elements added to it, relative to a provided
 * comparator. "Top" can mean the greatest or the lowest elements, specified in the factory used to
 * create the {@code TopKSelector} instance.
 *

And we need to get the dependency function from the module `app.dependencies`, the file `app/dependencies.py`.

So we use a relative import with `..` for the dependencies:

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[3] title["app/routers/items.py"] *}

#### How relative imports work { #how-relative-imports-work }

/// tip

If you know perfectly how imports work, continue to the next section below.

///

    /**
     * Returns the canonicalized UNC path of this SMB resource relative to its share.
     *
     * @return The canonicalized UNC path of this SMB resource (relative to it's share)
     */
    String getUNCPath();

    /**
     * Returns the canonicalized URL path relative to the server or domain.
     *
     * @return The canonicalized URL path (relative to the server/domain)
     */
    String getURLPath();

    /**

Bu yüzden dependency’ler için `..` ile relative import kullanıyoruz:

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[3] title["app/routers/items.py"] *}

#### Relative Import Nasıl Çalışır { #how-relative-imports-work }

/// tip | İpucu

Import’ların nasıl çalıştığını çok iyi biliyorsanız, bir sonraki bölüme geçin.

     * @throws IOException Model read problem
     */
    @Test
    void testFlatTrickyUrls() throws IOException {
        // parent references child with artifactId (which is not directory name)
        // then relative path calculation will fail during build from disk but success when calculated from repo
        try {
            // build from disk expected to fail
            testInheritance("tricky-flat-artifactId-urls", false);

# Deployment { #deployment }

Deploying a **FastAPI** application is relatively easy.

## What Does Deployment Mean { #what-does-deployment-mean }

To **deploy** an application means to perform the necessary steps to make it **available to the users**.