[
https://issues.apache.org/jira/browse/GERONIMO-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747776#comment-16747776
]
Romain Manni-Bucau commented on GERONIMO-6686:
----------------------------------------------
We don't force him to change his method name but to set an operationId in that
case. For the history part our default is swagger one from memory so don't
think changing it is that same so more i'm thinking about it more I think a
NamingStrategy makes sense. Wdyt?
> 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)
