Skip to content
New issue

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

AnnotationMethodHandlerAdapter should also implement Ordered interface [SPR-6516] #11182

Closed
spring-projects-issues opened this issue Dec 3, 2009 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Pavel Marinchev opened SPR-6516 and commented

The initHandlerAdapters(...) method in the DispatcherServlet class expects all the discovered adapters being sorted. It tries to keep them in sorted order. That's nice and makes sense. BTW, this strategy is working fine also for HandlerMapping implementations.

The bad thing is that the default implementation of HandlerAdapter interface being used for the annotation driven context (AnnotationMethodHandlerAdapter) doesn't support ordering. That makes some inconveniences for our team dealing with several contexts.

It would be nice if the AnnotationMethodHandlerAdapter class could also implement Ordered interface so that the DispatcherServlet could keep defined ordering for the handler adapters.

Thanks in advance!
Pavel


Affects: 3.0 RC3

Referenced from: commits f72769a

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 GA milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants