[ 
https://issues.apache.org/jira/browse/CAMEL-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keegan Witt updated CAMEL-11683:
--------------------------------
    Description: 
As a workaround to CAMEL-11528, we tried replacing something like 
{code:java}
 from("direct:start")
    .wireTap("bean:tap")
    .to("mock:result");
{code}
 
with
{code:java}
.from("direct:start")
    .to("direct:tap")
    .to("mock:result");

.from("direct:tap")
    .process("bean:tapper");
{code}

We got {noformat}Caused by: org.apache.camel.FailedToCreateRouteException: 
Failed to create route route190 at: >>> process[ref:bean:tapper] <<< in route: 
Route(route190)[[From[direct:tap]] -> [OnException[[clas... because of No bean 
could be found in the registry for: bean:genericMessageLogService of type: 
org.apache.camel.Processor{noformat}

But if we did
{code:java}
public class MyRoute extends RouteBuilder {
    @Resource Tapper tapper;

    public void configure() {
        from("direct:start")
            .wiretap("direct:tap")
            .to("mock:result");

        from("direct:tap")
            .process("bean:tapper");
    }
}
{code}
Where Tapper was a Camel Processor, it worked.

  was:
As a workaround to CAMEL-11528, we tried replacing something like 
{code:java}
 from("direct:start")
                    .wireTap("bean:tap").dynamicUri(false)
                    .to("mock:result");
{code}

In 2.15 we had references using 
[to(java.lang.String)|https://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/model/ProcessorDefinition.html#to(java.lang.String)]
 that referenced beans, like this
{code:java}
.from(foo)
.to("bean:myBean?method=processMethod1")
{code}

This no longer seems to work and I'm not sure if that was an intentionally 
breaking change.


> Allow bean references in to() URI
> ---------------------------------
>
>                 Key: CAMEL-11683
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11683
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.15.5
>            Reporter: Keegan Witt
>            Assignee: Claus Ibsen
>
> As a workaround to CAMEL-11528, we tried replacing something like 
> {code:java}
>  from("direct:start")
>     .wireTap("bean:tap")
>     .to("mock:result");
> {code}
>  
> with
> {code:java}
> .from("direct:start")
>     .to("direct:tap")
>     .to("mock:result");
> .from("direct:tap")
>     .process("bean:tapper");
> {code}
> We got {noformat}Caused by: org.apache.camel.FailedToCreateRouteException: 
> Failed to create route route190 at: >>> process[ref:bean:tapper] <<< in 
> route: Route(route190)[[From[direct:tap]] -> [OnException[[clas... because of 
> No bean could be found in the registry for: bean:genericMessageLogService of 
> type: org.apache.camel.Processor{noformat}
> But if we did
> {code:java}
> public class MyRoute extends RouteBuilder {
>     @Resource Tapper tapper;
>     public void configure() {
>         from("direct:start")
>             .wiretap("direct:tap")
>             .to("mock:result");
>         from("direct:tap")
>             .process("bean:tapper");
>     }
> }
> {code}
> Where Tapper was a Camel Processor, it worked.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to