[ 
https://issues.apache.org/jira/browse/CAMEL-10416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748926#comment-15748926
 ] 

Nicola Ferraro commented on CAMEL-10416:
----------------------------------------

I've developed a component (>90% finished) for this Jira few weeks ago and put 
it in standby.

The reason is that I don't know if it's worth adding it to camel because it 
doesn't seem much better than using camel-servlet on Spring-Boot.
The difference between the two is that this one intercepts requests after they 
have been handled by the spring framework (spring dispatcher servlet), rather 
than binding another Servlet to the context.

This allows using camel routes alongside other spring rest endpoints (eg. 
binding a route to "/users/xx", even if there is a spring endpoint on "/users") 
or binding camel routes to eg. "/endpoint1", "/endpoint2" without affecting eg. 
actuator endpoints (because in order to bind rest endpoints to "/endpointx" in 
camel servlet you have to set the context path to "/*" and so the requests are 
not dispatched to spring anymore).
It uses the internal multipart binding of the spring framework, eg. for caching 
attachments. It supports async communication as Spring does.

Do you think we should add it or drop it? [[email protected]], [~lb].

> spring-boot native support for REST DSL and servlet
> ---------------------------------------------------
>
>                 Key: CAMEL-10416
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10416
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-spring-boot
>            Reporter: Nicola Ferraro
>            Assignee: Nicola Ferraro
>             Fix For: 2.19.0
>
>
> It should be possible to use the REST DSL natively on top of the 
> spring-boot-web implementation, without the need to bind the Camel services 
> under a specific sub-root (eg. camel-servlet requires all your services being 
> under the "/camel/*" path or something else).
> Probably we need a component for that. With such a component, it would be 
> easier to switch between any of the spring-boot embedded servers (Tomcat, 
> Jetty, Undertow, ...) and reuse all the spring-boot features for what 
> concerns eg. configuration, health checks, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to