[jira] Resolved: (CAMEL-308) Test/Example how to use manage object using spring 2.5.1 features

["Hadrian Zbarcea (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea resolved CAMEL-308.
-----------------------------------

    Fix Version/s: 1.4.0
       Resolution: Fixed

Patch applied with thanks.  I had to make a few modifications, such as adding the Apache License comments and moved it to a different package due to interference with other tests.

> Test/Example how to use manage object using spring 2.5.1 features
> -----------------------------------------------------------------
>
>                 Key: CAMEL-308
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-308
>             Project: Apache Camel
>          Issue Type: Test
>          Components: camel-spring
>    Affects Versions: 1.3.0
>            Reporter: Przemyslaw Budzik
>            Assignee: Hadrian Zbarcea
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: spring251test.zip
>
>
> Could be added to the code or used on website as one of Spring integration examples. Typical Camel applications are usually not only simple RouteBuilders. There are many components like processors, beans woven in DSL. This piece of code shows how to make it cleaner using Spring features. The pattern is to have all (needed) pojos automatically scaned and registered in Camel-Spring context and injected to RouteBuilder avoiding initialization-hell.

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