We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring has the concept of multiple RequestMapping paths for a controller. I can't see a way to do something similar with Atmosphere.
We'd like something like:
@managedservice(path={"/api/subscribe/{id}", "/another/api/{id}"})
The text was updated successfully, but these errors were encountered:
What is the benefit? Do you have a use case?
Sorry, something went wrong.
The use case is for migrating and maintaining backward compatibility of an API without having rewrite rules or having two instances of the same class.
+1
No branches or pull requests
Spring has the concept of multiple RequestMapping paths for a controller. I can't see a way to do something similar with Atmosphere.
We'd like something like:
@managedservice(path={"/api/subscribe/{id}", "/another/api/{id}"})
The text was updated successfully, but these errors were encountered: