Rename opentracing-spring-web-handler-interceptor to something more appropriate
See original GitHub issueAll the instrumentations are using org.springframework#spring-webmvc
(spring web and http clients) and instrumentation artifactId is opentracing-spring-web-handler-interceptor
and auto-configuration opentracing-spring-web-autoconfigure
.
Should we change opentracing-spring-web-handler-interceptor
to something like opentracing-spring-web/opentracing-spring-webmvc
as it includes all instrumentations, both client and server side?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Rename opentracing-spring-web-autoconfigure to ... - GitHub
I propose to rename this project from opentracing-spring-web-autoconfigure to opentracing-spring-web-starter to adopt/follow the same convention ...
Read more >Introduction to Spring MVC HandlerInterceptor - Baeldung
In this tutorial, we'll focus on understanding the Spring MVC HandlerInterceptor and how to use it correctly.
Read more >Spring Cloud
Spring Cloud provides tools for developers to quickly build some of the common patterns in distributed systems (e.g. configuration management, ...
Read more >Spring MVC Interceptor HandlerInterceptorAdapter ...
web.servlet.handler.HandlerInterceptorAdapter that provides the base implementation of HandlerInterceptor interface. Spring Interceptor - ...
Read more >Chapter 9. Issues Resolved in Fuse 7.0
Rename the org.apache.felix.gogo.commands package to org.apache.karaf.shell.commands ... Karaf web console does not work on tabs features, http and instance.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think it may be better to consolidate all spring (-web) related framework integration into a single repo. Otherwise there is potentially alot of fragmentation for essentially the same technology stack.
Closing, implemented in https://github.com/opentracing-contrib/java-spring-web/pull/11