openapi4j is archived

[rlratcliffe]

Using the archetype with camel-rest-extensions, when migrating APIs where the specification paths cannot be changed, this path pattern collision issue sometimes occurs. There may be other bugs but this seems to be the most common one.

Since openapi4j is archived, it means there's no support for fixing bugs like this.

Alternative libraries:

• com.atlassian.oai swagger-request-validator-core is already part of this project and according to this camel-rest-extensions merged PR it was switched from because it didn't offer XML support, and there is still an open issue for XML support with the validator
• ?

[rlratcliffe]

My short term plan in order to support this for clients who need this fix is to fork the openapi4j version to fix the bug and then update camel-rest extensions to use the forked version.

Long term, I don't think it's a good idea to use a forked openapi4j version that we would also need to maintain. But switching to a whole new validator library requires significantly more changes and figuring out the acceptance criteria to ensure previous functionality is not broken.

[rlratcliffe]

Short term plan is complete: Released new openapi4j on github: https://github.com/MS3Inc/openapi4j/releases/tag/MS3-1.0.8 Released snapshot version of camel-rest-extensions: https://github.com/MS3Inc/camel-rest-extensions/releases/tag/0.1.7-SNAPSHOT Updated archetype branch (not merged to main yet): https://github.com/MS3Inc/camel-archetypes/tree/version-updates