Wildcard annotations in @PATH dropped in swagger

[harveycggit]

When I use the plugin swagger-maven-plugin-jakarta to create swagger from my java annotations, any wildcards in @path annotations are dropped. For instance:

@path("/sws/{var:.*}")
@get
@produces(MediaType.TEXT_XML)

results in:

/v1/sws/{var}:
get:
description: Proxy banner SOAP GET
operationId: serveGet
etc

Which means that I get a 404 when calling a path such as https://myserver.com/api/v1/sws/housing/studentAccountService.xml

Note that jakarta has no problem handling this; when I hit the application on my desktop it works just fine, but because I am generating swagger dynamically to populate my 3scale gateway, 3scale does not understand that it is a wildcard path because swagger-maven-plugin-jakarta has removed the wildcard.

Is there any way to retain the wildcards when the swagger is generated?

[frantuma]

OpenAPI specification only allows path templating and Swagger Core drops the regex part accordingly, as it would be not valid.

#4415 introduces a slightly better support by adding pattern to path parameter