[BUG][JAVA] When package is @NullMarked, optional parameters are not @Nullable

[OrangeDog]

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

When useJspecify is enabled, all generated packages are @NullMarked.
However, optional request parameters are not marked with @Nullable, causing verification failures when they are not provided.

openapi-generator version

org.openapitools:openapi-generator-maven-plugin:7.22.0

OpenAPI declaration file content or url

openapi: 3.1.0
info:
  title: Test
  version: v1
paths:
  /test:
    get:
      parameters:
        - name: optional
          in: query
          required: false
          schema:
            type: string
      responses:
        200:
          description: success
          content:
            'application/json':
              schema:
                type: string

Generation Details

<configuration>
  <inputSpec>src/main/resources/test.yaml</inputSpec>
  <generatorName>java</generatorName>
  <library>resttemplate</library>
  <apiPackage>com.example</apiPackage>
  <invokerPackage>com.example.client</invokerPackage>
  <modelPackage>com.example.model</modelPackage>
  <generateModelTests>false</generateModelTests>
  <generateModelDocumentation>false</generateModelDocumentation>
  <generateApiTests>false</generateApiTests>
  <generateApiDocumentation>false</generateApiDocumentation>
  <ignoreFileOverride>.openapi-generator-ignore</ignoreFileOverride>
  <configOptions>
    <generateClientAsBean>true</generateClientAsBean>
    <openApiNullable>false</openApiNullable>
    <useAbstractionForFiles>true</useAbstractionForFiles>
    <useJackson3>true</useJackson3>
    <useJakartaEe>true</useJakartaEe>
    <useJspecify>true</useJspecify>
    <useSpringBoot4>true</useSpringBoot4>
  </configOptions>
</configuration>

Steps to reproduce

Generate with the above settings.

Observed output

@org.jspecify.annotations.NullMarked
package com.example;

package com.example;

// [...]

    /**
     * 
     * 
     * <p><b>200</b> - success
     * @param optional  (optional)
     * @return String
     * @throws RestClientException if an error occurs while attempting to invoke the API
     */
    public String testGet(String optional) throws RestClientException {
        return testGetWithHttpInfo(optional).getBody();
    }

Expected output

    public String testGet(@Nullable String optional) throws RestClientException {
        return testGetWithHttpInfo(optional).getBody();
    }

[faltfe]

I have the same problem and after some debugging it is even more complexe. The first generated endpoint uses @Nullable wrong. Let me give an example

openapi: 3.1.0
info:
  title: Test
  version: v1
paths:
    /foobar/{foobarId}/abort:
    post:
      description: first in alphabet
      operationId: abort
      parameters:
        - $ref: "#/components/parameters/FoobarId"
      requestBody:
        $ref: "#/components/requestBodies/FoobarBody"
      responses:
        "200":
          description: Foobar

  /foobar/{foobarId}/approve:
    post:
      description: second in alphabet
      operationId: approve
      parameters:
        - $ref: "#/components/parameters/FoobarId"
      requestBody:
        $ref: "#/components/requestBodies/FoobarBody"
      responses:
        "200":
          description: Foobar

components:
  parameters:
    ApprovalRequestId:
      in: path
      name: foobarId
      required: true
      schema:
        $ref: "#/components/schemas/UUID"
  schemas:
        UUID:
          type: string
          format: uuid

It will generate something like

    ResponseEntity<Void> abort(
        @Parameter(name = "foobarId", description = "", required = true, in = ParameterIn.PATH) @PathVariable("foobarId") @Nullable UUID foobarId);
...
    ResponseEntity<Void> approve(
        @Parameter(name = "foobarId", description = "", required = true, in = ParameterIn.PATH) @PathVariable("approvalId") UUID approvalId);

The @Nullable is only added for the first generated endpoint. All others are generated correctly as far as I tested it.

My maven configuration is a little different:

<generatorName>spring</generatorName>
<configOptions>
    <interfaceOnly>true</interfaceOnly>
    <requestMappingMode>api_interface</requestMappingMode>
    <skipDefaultInterface>true</skipDefaultInterface>
    <useSpringBoot4>true</useSpringBoot4>
    <useJackson3>true</useJackson3>
    <openApiNullable>true</openApiNullable>
    <useJspecify>true</useJspecify>
    <performBeanValidation>true</performBeanValidation>
</configOptions>