[
https://issues.apache.org/jira/browse/GERONIMO-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747747#comment-16747747
]
Dennis Kieselhorst commented on GERONIMO-6686:
----------------------------------------------
Assume the user hasn't set an operationId, do we want to force him to change
his method names? I've looked at other implementations and it seems they
consider the path or append a number to get it unique.
I'm currently working on other topics, so feel free to take this one :)
> OpenAPI operationId is not unique
> ---------------------------------
>
> Key: GERONIMO-6686
> URL: https://issues.apache.org/jira/browse/GERONIMO-6686
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Dennis Kieselhorst
> Priority: Major
> Fix For: OpenAPI_1.0.5
>
>
> Spec says:
> _{{operationId}} is an optional unique string used to identify an operation.
> If provided, these IDs must be unique among all operations described in your
> API._
> Currently if two resource classes provide a method with the same name the
> operationId is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
