+1 -----Original Message----- From: Dragisa Krsmanovic [mailto:dkrsmano...@plos.org] Sent: Thursday, April 08, 2010 1:29 PM To: users@camel.apache.org Subject: Re: Move to Spring 3.0
We run our Camel 2.2.0 app with Spring 3.0 (3.0.1 and 3.0.2 now) without problems. On Thu, 2010-04-08 at 00:51 -0700, umairt wrote: > Hi, > > > I am trying to shift my project(currently using Camel2.2.0 and Spring 2.5) > to spring 3.0. I have changed the spring version to 3 but I am getting the > following stack trace: > > orCaused by: java.lang.NullPointerException > at org.apache.camel.impl.ProducerCache.<init>(ProducerCache.java:52) > at > org.apache.camel.impl.DefaultProducerTemplate.<init>(DefaultProducerTemplate.java:57) > at > org.apache.camel.spring.CamelProducerTemplateFactoryBean.getObject(CamelProducerTemplateFactoryBean.java:74) > at > org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142) > > After I debugged it I found something very strange in > CamelProducerTemplateFactoryBean. The getObject method is being called > before afterPropertiesSet method is called. That is why camel context is > uninitialized and hence the null pointer exception. I was wondering how this > could happen in Spring or am I missing some camel configuration for spring > 3.0? > > > Umair -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This email is confidential to the intended recipient. If you have received it in error, please notify the sender and delete it from your system. Any unauthorized use, disclosure or copying is not permitted. The views or opinions presented are solely those of the sender and do not necessarily represent those of Public Library of Science unless otherwise specifically stated. Please note that neither Public Library of Science nor any of its agents accept any responsibility for any viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any).
