Investigate possible implementation of SpringIntegrationServlet that would map its handler based on the arbitrary attribute (e.g., 'path') rather than beanName for non-MVC cases [INT-2102]

[spring-operator]

Oleg Zhurakousky opened INT-2102 and commented

Currently there is an effort to refactor Http Inbound adapters to provide support for mapping UriVariables. See #5673. That created a lot of ideas on how Http Inbound adapters could be improved. One of the ideas is to rely on 'path' attribute rather than beanName. For Spring-MVC based cases where DispatcherServlet is present all we need is register our own implementation of HandlerMapping (essentially override the default one). We can do it by subclassing BeanNameUrlHandMapping so it can still handle bean names (so you can have conventional controllers in the AC) and add 'path' detection logic. We can register it in the parser.

For non MVC cases we can provide our own servlet implementation for convinience that will provide mapping to the handler based on 'path' attribute. We already have something similar in Spring where we have DefaultServletHttpRequestHandler which maps itself to a well known servlet names (e.g., Google App Engine, JBoss etc.)

---

Affects: 2.0.5

Issue Links:

• Ability to access parameters from HTTP GET inbound requests when constructing outbound calls [INT-1677] #5673 Ability to access parameters from HTTP GET inbound requests when constructing outbound calls
  ("depends on")

[spring-operator]

Mark Fisher commented

I think the UriPathHandlerMapping that has already been implemented is sufficient.