You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
There is already a request name determiner for Spring MVC projects. We are using Resteasy for our projects and will be implementing a similar mechanism for Resteasy requests. Before I implement it I wanted to see if there was a preference on how it names things.
We would prefer if it did something like ResourceClass#requestMethod which is different from what the Spring MVC request names are. Would this difference be OK?
The text was updated successfully, but these errors were encountered:
Maybe a good way would be to have a configurable naming strategy or something. That way you could configure how to name things in one place.
For example, NamingStrategy.METHOD would behave like the default and NamingStrategy.CLASS_METHOD would be like your suggestion.
There is already a request name determiner for Spring MVC projects. We are using Resteasy for our projects and will be implementing a similar mechanism for Resteasy requests. Before I implement it I wanted to see if there was a preference on how it names things.
We would prefer if it did something like
ResourceClass#requestMethod
which is different from what the Spring MVC request names are. Would this difference be OK?The text was updated successfully, but these errors were encountered: