Hi.
Ok Thanks, The error seems goes way now.
I am still running Spring 4.3.20, Camel 2.21.5, Tomcat 9.0.12 and open JDK
11.0.3
Previously in the Spring XM looks like this and it works and runs in production
on camel 2.8
<camel:camelContext id="customer-services"
xmlns="http://camel.apache.org/schema/spring";>
<contextScan>
<includes> xx.xx.xxx.*</includes>
</contextScan>
</camel:camelContext>
<camel:proxy id="customersAdminProxy"
serviceInterface="xx.xx.xxx.CustomersAdminService"
serviceUrl="vm:customerAdminService" />
<camel:proxy id="importLogProxy"
serviceInterface=" xx.xx.xxx.ImportLogService"
serviceUrl="vm:importLogService" />
And I am getting this vm component issue when I try to upgrade the project to a
higher version of Camel.
But the error seems goes away now when I put the <proxy> inside of the
<camelContext>,
<camel:camelContext id="customer-services"
xmlns="http://camel.apache.org/schema/spring";>
<contextScan>
<includes> xx.xx.xxx.*</includes>
</contextScan>
<camel:proxy id="customersAdminProxy"
serviceInterface="xx.xx.xxx.CustomersAdminService"
serviceUrl="vm:customerAdminService" />
<camel:proxy id="importLogProxy"
serviceInterface=" xx.xx.xxx.ImportLogService"
serviceUrl="vm:importLogService" />
</camel:camelContext>
Best regards
Steve Pan
-----Original Message-----
From: Claus Ibsen <[email protected]>
Sent: Thursday, 18 July 2019 14:42
To: [email protected]
Subject: Re: Cannot auto create component: vm
Hi
Try with a newer Camel version
On Thu, Jul 18, 2019 at 11:55 AM Steve Pan <[email protected]> wrote:
>
> Thanks Camel.
>
> I am now trying to migrate the project to Spring 4.3.20 and Camel
> 2.21.5 Still running on Tomcat 9.0.12 and open JDK 11.0.3
>
> I am still having problem with the vm component, but this time I get another
> error.
>
> In my Spring XML I have two camel proxy:
>
> <camel:proxy id="customersAdminProxy"
> serviceInterface="xx.xx.xxx.CustomersAdminService"
> serviceUrl="vm:customerAdminService" />
>
> <camel:proxy id="importLogProxy"
> serviceInterface="xx.xx.xxx.ImportLogService"
> serviceUrl="vm:importLogService" />
>
>
> and I get this error.
> "2019-07-18 11:25:19,151 WARN
> [org.springframework.beans.factory.support.DefaultListableBeanFactory] - Bean
> creation exception on non-lazy FactoryBean type check:
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'importLogProxy': Invocation of init method failed; nested
> exception is org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: vm://importLogService due to: Circular dependency detected,
> the component vm is already being created"
>
> It seems customersAdminProxy was created successfully, but importLogProxy
> failed due to compoment vm was created by customersAdminProxy?
>
> Any idea how I should trouble shoot this error?
>
> Best regards
> Steve Pan
>
>
> -----Original Message-----
> From: Claus Ibsen <[email protected]>
> Sent: Wednesday, 17 July 2019 16:45
> To: [email protected]
> Subject: Re: Cannot auto create component: vm
>
> Hi
>
> Java 11 is not supported with this older version of Camel. Try with a
> newer version of Camel
>
> On Wed, Jul 17, 2019 at 3:56 PM Steve Pan <[email protected]> wrote:
> >
> > Hi.
> > I am trying to migrate a project from Spring 3.0.3 and camel 2.8.3
> > to Spring 4.1.5 and camel 2.15.0 I am trying to run it on Tomcat
> > 9.0.12 and open JDK 11.0.3
> >
> > And in my spring xml, there is a proxy as below <camel:proxy
> > id="importLogProxy"
> > serviceInterface="xxx.xxx.xx.ImportLogService"
> > serviceUrl="vm:importLogService" />
> >
> >
> > But I get “Cannot auto create component: vm” error? Any idea why vm
> > component can´t be auto created?
> > 2019-07-17 14:30:30,225 WARN
> > [org.springframework.beans.factory.support.DefaultListableBeanFactor
> > y]
> > - Bean creation exception on FactoryBean type check:
> > org.springframework.beans.factory.BeanCreationException: Error
> > creating bean with name 'importLogProxy': Invocation of init method
> > failed; nested exception is
> > org.apache.camel.ResolveEndpointFailedException: Failed to resolve
> > endpoint: vm://importLogService due to: Cannot auto create component:
> > vm
> >
> > I also tried with direct, direct-vm and seda. They seems to work but vm
> > does not.
> >
> > How should I trouble shoot this?
> >
> > Best regards
> > Steve Pan
> >
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
