[
https://issues.apache.org/jira/browse/CAMEL-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417807#comment-17417807
]
Piotr Klimczak commented on CAMEL-16183:
----------------------------------------
[~davsclaus] I think community (or at least myself) would be thankful if you
could provide a "good" practice to achieve the same :) for spring apps.
We have few development teams, where one is fore example core devs and other
integration devs (like myself).
We use interfaces exposed Spring beans for core devs, which are wired using
camel spring proxy to camel routes (internal REST APIs client side).
We don't want to use pure REST without camel, as camel brings all the well
known benefits (debugging, tracing, stats etc).
So is the only solution in Camel 3.9+ to simply introduce our own proxy
solution, which then will use producer templates?
It would be nice for the release notes to mention how to actually achieve the
same without it.
I am sure there are quite few people who use it like my in my projects for
years.
> camel-spring - XML DSL remove remoting/proxy
> --------------------------------------------
>
> Key: CAMEL-16183
> URL: https://issues.apache.org/jira/browse/CAMEL-16183
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.9.0
>
>
> Part of the modularization of camel-spring then we are removing 2 spring only
> features in the XML DSL (not in blueprint or cdi xml) which are very old
> features of spring that is not good practice to use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
