Return-Path: 
 <dev-return-14653-apmail-camel-dev-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-dev-archive@www.apache.org
Received: (qmail 49593 invoked from network); 27 Oct 2009 11:04:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 27 Oct 2009 11:04:15 -0000
Received: (qmail 84038 invoked by uid 500); 27 Oct 2009 11:04:15 -0000
Delivered-To: apmail-camel-dev-archive@camel.apache.org
Received: (qmail 83977 invoked by uid 500); 27 Oct 2009 11:04:15 -0000
Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@camel.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@camel.apache.org>
List-Post: <mailto:dev@camel.apache.org>
List-Id: <dev.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list dev@camel.apache.org
Received: (qmail 83967 invoked by uid 500); 27 Oct 2009 11:04:15 -0000
Delivered-To: apmail-activemq-camel-dev@activemq.apache.org
Received: (qmail 83964 invoked by uid 99); 27 Oct 2009 11:04:15 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 11:04:15 +0000
X-ASF-Spam-Status: No, hits=-10.5 required=5.0
	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 11:04:12 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id C6CEE234C045
	for <camel-dev@activemq.apache.org>; Tue, 27 Oct 2009 04:03:52 -0700 (PDT)
Message-ID: <1327542887.1256641432805.JavaMail.jira@brutus>
Date: Tue, 27 Oct 2009 04:03:52 -0700 (PDT)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2112) Problem using a
 CamelTransportFactory from a junit 4 unit test or together with
 <context:annotation-config/>
In-Reply-To: <1205699319.1256628952680.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c


    [ https://issues.apache.org/activemq/browse/CAMEL-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55010#action_55010 ] 

Willem Jiang commented on CAMEL-2112:
-------------------------------------

@ Christian,

I just got time to check your test-case and stack trace. From the stack trace , it looks like CamelTransportFactory has a wrong annotated field, and the spring JSR250 can't find a right value to inject. Removed the @Resource annotation from  public void setActivationNamespaces(Collection<String> ans) resolved this issue.

BTW,  there are some explanation of the CXF JSR250 PostProcessor in [CXF-2210|https://issues.apache.org/jira/browse/CXF-2210] which shows CXF JSR250PostProcessor can work with Spring JSR250 PostProcessor.

> Problem using a CamelTransportFactory from a junit 4 unit test or together with <context:annotation-config/>
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2112
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2112
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.0.0
>            Reporter: Christian Schneider
>         Attachments: cxfcamelexample.zip, stack trace.txt
>
>
> I recently tried to convert my unit tests to junit 4 using the new Spring test framework.
> Since then I get the following exception when calling the test.
> Error creating bean with name 'org.apache.camel.component.cxf.transport.CamelTransportFactory#0': Injection of resource methods failed; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [java.lang.String] found for dependency [collection of java.lang.String]: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}
> The same happens when I activate /<context:annotation-config/>/
> I think it has to do with autowiring. Do you have any idea what goes wrong here and how I can fix it? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.