[
https://issues.apache.org/jira/browse/CAMEL-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021188#comment-18021188
]
Gardella Juan Pablo commented on CAMEL-21556:
---------------------------------------------
[~davsclaus] actually it is working as described at
[https://camel.apache.org/manual/rest-dsl.html#_inline_rest_dsl_as_a_single_route].
We have a route like:
{code:xml}
<rest>
<get path="/customers/{id}">
<to uri="direct:customerDetail"/>
</get>
{code}
And we have a test trying to call _direct:customerDetail_ and, according the
documentation, that will not work.
_Notice the REST services above each use a unique 1:1 linked direct endpoint
(direct:customerDetail, direct:customerOrders direct:customerNewOrder). This
means that you cannot call these routes from another route such as the
following would not function:_
That broke existing application with ton of rest operations. We had to disable
that option to keep this working.
> REST route inlining is causing errors when a REST and timer is defined in the
> same RouteBuilder
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-21556
> URL: https://issues.apache.org/jira/browse/CAMEL-21556
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Darius Cooper
> Priority: Minor
> Attachments: MessageProcessingRoute.groovy
>
>
> Related to:
> [https://camel.apache.org/manual/rest-dsl.html#_inline_rest_dsl_as_a_single_route]
> When updating from camel 4.4 to 4.8 we encountered a
> _DirectConsumerNotAvailableException_ from our timer/cron routes that share a
> direct route with a REST endpoint. In this example the exception was being
> thrown for "direct:process" not being available. The REST endpoints
> continued to function successfully.
> I updated the property camel.rest.inline-routes = false and the timer routes
> began working and was able to find "direct:process". It appears that when
> REST inlining is true it is configuring "direct:process" in a way that other
> routes cannot access it.
> See attached example[^MessageProcessingRoute.groovy]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
