byte[] outputBytes, int ioctlFlags) {
        final int headerLen = 64; // SMB2 header is 64 bytes
        final int bodyFixed = 48; // body size minus 1 for structure size field overlap
        final int payloadStart = headerLen + bodyFixed;
        final int bodyLen = bodyFixed + inputCount + outputCount;

        byte[] buf = new byte[bodyLen];
        int pos = 0;

    int NT_STATUS_ACCOUNT_DISABLED = 0xC0000072;
    /** No mapping between account names and security IDs was done */
    int NT_STATUS_NONE_MAPPED = 0xC0000073;
    /** The security ID structure is invalid */
    int NT_STATUS_INVALID_SID = 0xC0000078;
    /** The disk is full */
    int NT_STATUS_DISK_FULL = 0xC000007f;
    /** Insufficient resources are available to complete the request */

type PostPolicyForm struct {
	Expiration time.Time // Expiration date and time of the POST policy.
	Conditions struct {  // Conditional policy structure.
		Policies []struct {
			Operator string
			Key      string
			Value    string
		}
		ContentLengthRange contentLengthRange
	}
}

// implemented to ensure that duplicate keys in JSON

De esta manera, su esquema aparecerá en la interfaz de usuario de la documentación de la API:

<img src="/img/tutorial/dataclasses/image01.png">

## Dataclasses en Estructuras de Datos Anidadas { #dataclasses-in-nested-data-structures }

También puedes combinar `dataclasses` con otras anotaciones de tipos para crear estructuras de datos anidadas.

Dessa forma, seu esquema aparecerá na interface de documentação da API:

<img src="/img/tutorial/dataclasses/image01.png">

## Dataclasses em Estruturas de Dados Aninhadas { #dataclasses-in-nested-data-structures }

Você também pode combinar `dataclasses` com outras anotações de tipo para criar estruturas de dados aninhadas.

        assertEquals(0x0311, response.getDialectRevision());
        assertNotNull(response.getServerGuid());
    }

    @ParameterizedTest
    @DisplayName("Should throw exception for invalid structure size")
    @ValueSource(ints = { 0, 1, 64, 66, 128 })
    void testReadBytesWireFormatInvalidStructureSize(int structureSize) {
        // Given
        byte[] buffer = new byte[256];

            // Create a buffer and write
            byte[] buffer = new byte[256];
            int bytesWritten = request.writeBytesWireFormat(buffer, 64);

            // Verify structure size (should be 41)
            assertEquals(41, SMBUtil.readInt2(buffer, 64));

            // Verify info type and file info class
            assertEquals((byte) 0x01, buffer[66]);

///

/// tip

Notice how each model's attribute with a type, default value and `Field` has the same structure as a *path operation function's* parameter, with `Field` instead of `Path`, `Query` and `Body`.

///

## Add extra information { #add-extra-information }

        In the rare cases where this is infeasible, we will also accept a detailed set of instructions.
        You can also use [Gradle Project Replicator](https://github.com/android/project-replicator) to reproduce the structure of your project.
    validations:
      required: true
  - type: input
    id: gradle-version
    attributes:
      label: Gradle version
      description: What version of Gradle are you running?

 */
package jcifs.internal.fscc;

import java.nio.charset.StandardCharsets;

import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;

/**
 * File System Control Code (FSCC) structure for File Rename Information.
 * Used in SMB2/SMB3 set file information operations to rename files or directories,
 * with support for specifying whether to replace existing files with the same name.
 *
 * @author mbechler