Hi Henryk, In CXF 3.0 the dependency of SingleConnectionFactory102 is removed, so this issue could be resolve when we upgrade the CXF version to next milestone release of CXF 3.0.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 9, 2014 at 4:36:33 PM, Henryk Konsek (hekon...@gmail.com) wrote: > > > Thanks Christian. Let's figure out then if the build passes. > I created > > Jira ticket for this task [2]. > > According to the Jenkins (1) we got three tests issues related > to > Spring API upgrade: > > org.apache.camel.component.cxf.jms.CxfEndpointJMSConsumerTest.testInvocation > org.apache.camel.example.cxf.httptojms.CxfHttpJmsClientServerTest.testClientInvocation > > org.apache.camel.testng.patterns.DebugSpringTest.setUp > > The CXF errors are cause by CXF using deprecated Spring 3 API for > JMS. > Maybe someone from CXF community could tell us more about perspectives > for switching from deprecated > org.springframework.jms.connection.SingleConnectionFactory102 > to > recommended org.springframework.jms.connection.SingleConnectionFactory? > > (1) > https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.spring4/1/ > > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com >
