camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2112) Problem using a CamelTransportFactory from a junit 4 unit test or together with <context:annotation-config/>
Date Tue, 27 Oct 2009 11:03:52 GMT

    [ 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.


Mime
View raw message