Java AsyncAPI generator bug?

[QuinnBast]

Hello, I am trying to use the asyncAPI CLI generator, but it seems to not work. Maybe I am doing something wrong?

I have a very basic AsyncAPI file:

asyncapi: 3.1.0
info:
  title: Brain Kafka AsyncAPI
  version: 1.0.0
  description: |
    Sample API Documentation

defaultContentType: application/json

servers:
  kafka:
    host: kafka-cluster:9092
    protocol: kafka
    description: Default Kafka bootstrap server (example).

channels:
  schedule-optimization-request:
    address: schedule-optimization-request
    title: Schedule Optimization Request
    description: Request to create a new schedule for optimization tasks.
    servers:
      - $ref: '#/servers/kafka'
    messages:
      CreateScheduleRequest:
        name: CreateScheduleRequest
        title: CreateScheduleRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/CreateScheduleRequest'

In the rendered AsyncAPI documentation, the $ref works and correctly references my object in the other file.

But when I attempt to use the asyncapi generator, I run this in my gradle:

val asyncapiGenerate = tasks.register<Exec>("asyncapiGenerate") {
    commandLine(
        "asyncapi",
        "generate",
        "client",
        "java",
        "--no-interactive",
        "--debug",
        "-i",
        "$projectDir/asyncapi.yaml",
        "-o",
        "$projectDir/build/generated/asyncapi",
    )
}

But I end up getting the following error:

Transpilation of files /home/almalinux/.nvm/versions/node/v25.0.0/lib/node_modules/@asyncapi/cli/node_modules/@asyncapi/generator/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/template into /home/almalinux/.nvm/versions/node/v25.0.0/lib/node_modules/@asyncapi/cli/node_modules/@asyncapi/generator/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/__transpiled started.
File /home/almalinux/.nvm/versions/node/v25.0.0/lib/node_modules/@asyncapi/cli/node_modules/@asyncapi/generator/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/hooks couldn't be found. Error: ENOENT: no such file or directory, stat '/home/almalinux/.nvm/versions/node/v25.0.0/lib/node_modules/@asyncapi/cli/node_modules/@asyncapi/generator/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/hooks'
File /home/almalinux/Documents/gxrms/gxrms/libraries/api/brain-api/build/generated/asyncapi/src/main/resources/AppProperties.js couldn't be found. Error: ENOENT: no such file or directory, stat '/home/almalinux/Documents/gxrms/gxrms/libraries/api/brain-api/build/generated/asyncapi/src/main/resources/AppProperties.js'
Successfully rendered template and wrote file src/main/resources/AppProperties.js to location: /home/almalinux/Documents/gxrms/gxrms/libraries/api/brain-api/build/generated/asyncapi/src/main/resources/AppProperties.js
File /home/almalinux/Documents/gxrms/gxrms/libraries/api/brain-api/build/generated/asyncapi/src/main/java/com/asyncapi/client.java.js couldn't be found. Error: ENOENT: no such file or directory, stat '/home/almalinux/Documents/gxrms/gxrms/libraries/api/brain-api/build/generated/asyncapi/src/main/java/com/asyncapi/client.java.js'

Generator Error: Server name must be provided.

Same issue if I try to run it just from the command line.

Am I doing something wrong? Or is the AsyncAPI generator CLI just broken? How do I specify a server name? This doesn't seem documented.

[QuinnBast]

Solved by joining the slack, but I have more problems.
https://asyncapi.slack.com/archives/C072JMTJ85Q/p1769596654223069

Lukasz Gornicki  [7:59 AM]
did you pass property required to specify server name?
[8:00 AM]something like -p server=production

This is definitely not documented anywhere, but adding -p server=kafka got me past this error.

However, even after generation, I am not getting any of my classes generated...

Also, I was kind of just expecting the java classes to be generated, not to be provided with an entire maven project. But after generation it seems that my types don't even exist.

Edit: Further update, I have added additional data types that I wanted to generate to my asyncapi spec and I am now also getting this error:

Generator Error: Cannot read properties of undefined (reading 'replace')

My AsyncApi spec is a lot larger now though... but here you go:

asyncapi: 3.0.0
info:
  title: AsyncAPI
  version: 1.0.0
  description: |
    AsyncAPI spec

defaultContentType: application/json

servers:
  kafka:
    host: kafka-cluster:9092
    protocol: kafka
    description: Default Kafka bootstrap server (example).

channels:
  schedule-optimization-request:
    description: Request to create a new schedule
    messages:
      CreateScheduleRequest:
        name: CreateScheduleRequest
        title: CreateScheduleRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/CreateScheduleRequest'

  schedule-optimization-response:
    description: Response indicating the result of a schedule creation request.
    messages:
      CreateScheduleResponse:
        name: CreateScheduleResponse
        title: CreateScheduleResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/CreateScheduleResponse'

  get-scheduled-optimizations-request:
    description: Request to retrieve all currently scheduled optimizations.
    messages:
      GetScheduledOptimizationsRequest:
        name: GetScheduledOptimizationsRequest
        title: GetScheduledOptimizationsRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetScheduledOptimizationsRequest'

  get-scheduled-optimizations-response:
    description: Response containing all currently scheduled optimizations.
    messages:
      GetScheduledOptimizationsResponse:
        name: GetScheduledOptimizationsResponse
        title: GetScheduledOptimizationsResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetScheduledOptimizationsResponse'

  delete-schedule-request:
    description: Request to delete an existing schedule.
    messages:
      DeleteScheduleRequest:
        name: DeleteScheduleRequest
        title: DeleteScheduleRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/DeleteScheduleRequest'

  delete-schedule-response:
    description: Response indicating the result of a schedule deletion request.
    messages:
      DeleteScheduleResponse:
        name: DeleteScheduleResponse
        title: DeleteScheduleResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/DeleteScheduleResponse'

  brain-get-all-rmps-request:
    description: Request to retrieve data
    messages:
      GetAllRmpsRequest:
        name: GetAllRmpsRequest
        title: GetAllRmpsRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetAllRmpsRequest'

  brain-get-all-rmps-response:
    description: Response containing all data
    messages:
      GetAllRmpsResponse:
        name: GetAllRmpsResponse
        title: GetAllRmpsResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetAllRmpsResponse'

  brain-get-rmp-by-id-request:
    description: Request to retrieve data by ID
    messages:
      GetRmpByIdRequest:
        name: GetRmpByIdRequest
        title: GetRmpByIdRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetRmpByIdRequest'

  brain-get-rmp-by-id-response:
    description: Response containing data
    messages:
      GetRmpByIdResponse:
        name: GetRmpByIdResponse
        title: GetRmpByIdResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/GetRmpByIdResponse'

  list-optimizations-request:
    description: Request to list optimizations.
    messages:
      ListOptimizationsRequest:
        name: ListOptimizationsRequest
        title: ListOptimizationsRequest
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/ListOptimizationsRequest'

  list-optimizations-response:
    description: Response containing the list of optimizations.
    messages:
      ListOptimizationsResponse:
        name: ListOptimizationsResponse
        title: ListOptimizationsResponse
        payload:
          $ref: './coordinator-api.yaml#/components/schemas/ListOptimizationsResponse'

  run-optimization-request:
    description: Runs optimizations immediately
    messages:
      RunOptimizationRequest:
        name: RunOptimizationRequest
        title: RunOptimizationRequest
        payload:
          $ref: './worker-api.yaml#/components/schemas/RunOptimizationRequest'

  run-optimization-response:
    description: Response of optimization
    messages:
      RunOptimizationResponse:
        name: RunOptimizationResponse
        title: RunOptimizationResponse
        payload:
          $ref: './worker-api.yaml#/components/schemas/RunOptimizationResponse'

operations:
  createSchedule:
    action: send
    channel:
      $ref: '#/channels/schedule-optimization-request'
    messages:
      - $ref: '#/channels/schedule-optimization-request/messages/CreateScheduleRequest'

  createScheduleResponse:
    action: receive
    channel:
      $ref: '#/channels/schedule-optimization-response'
    messages:
      - $ref: '#/channels/schedule-optimization-response/messages/CreateScheduleResponse'

  getScheduledOptimizations:
    action: send
    channel:
      $ref: '#/channels/get-scheduled-optimizations-request'
    messages:
      - $ref: '#/channels/get-scheduled-optimizations-request/messages/GetScheduledOptimizationsRequest'

  getScheduledOptimizationsResponse:
    action: receive
    channel:
      $ref: '#/channels/get-scheduled-optimizations-response'
    messages:
      - $ref: '#/channels/get-scheduled-optimizations-response/messages/GetScheduledOptimizationsResponse'

  deleteSchedule:
    action: send
    channel:
      $ref: '#/channels/delete-schedule-request'
    messages:
      - $ref: '#/channels/delete-schedule-request/messages/DeleteScheduleRequest'

  deleteScheduleResponse:
    action: receive
    channel:
      $ref: '#/channels/delete-schedule-response'
    messages:
      - $ref: '#/channels/delete-schedule-response/messages/DeleteScheduleResponse'

  getAllRmps:
    action: send
    channel:
      $ref: '#/channels/brain-get-all-rmps-request'
    messages:
      - $ref: '#/channels/brain-get-all-rmps-request/messages/GetAllRmpsRequest'

  getAllRmpsResponse:
    action: receive
    channel:
      $ref: '#/channels/brain-get-all-rmps-response'
    messages:
      - $ref: '#/channels/brain-get-all-rmps-response/messages/GetAllRmpsResponse'

  getRmpById:
    action: send
    channel:
      $ref: '#/channels/brain-get-rmp-by-id-request'
    messages:
      - $ref: '#/channels/brain-get-rmp-by-id-request/messages/GetRmpByIdRequest'

  getRmpByIdResponse:
    action: receive
    channel:
      $ref: '#/channels/brain-get-rmp-by-id-response'
    messages:
      - $ref: '#/channels/brain-get-rmp-by-id-response/messages/GetRmpByIdResponse'

  listOptimizations:
    action: send
    channel:
      $ref: '#/channels/list-optimizations-request'
    messages:
      - $ref: '#/channels/list-optimizations-request/messages/ListOptimizationsRequest'

  listOptimizationsResponse:
    action: receive
    channel:
      $ref: '#/channels/list-optimizations-response'
    messages:
      - $ref: '#/channels/list-optimizations-response/messages/ListOptimizationsResponse'

  runOptimization:
    action: send
    channel:
      $ref: '#/channels/run-optimization-request'
    messages:
      - $ref: '#/channels/run-optimization-request/messages/RunOptimizationRequest'

  runOptimizationResponse:
    action: receive
    channel:
      $ref: '#/channels/run-optimization-response'
    messages:
      - $ref: '#/channels/run-optimization-response/messages/RunOptimizationResponse'