camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-665) Document - how does Camel kickstart itself
Date Thu, 12 Mar 2009 10:49:40 GMT

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

Claus Ibsen resolved CAMEL-665.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.0.0)

> Document - how does Camel kickstart itself 
> -------------------------------------------
>
>                 Key: CAMEL-665
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-665
>             Project: Apache Camel
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>
> I do think we should have a more clear picture how Camel kick-starts itself. Currently
you can do it in several ways according to your needs and Camel is pretty smart in that regard.
> You can start Camel with:
> - Standalone with your own java main code
> - Using camel-spring Main class
> - From maven tools
> - Spring configured (a normal use-case)
> - Web-app with spring configured
> - OSGi activator (or how does it do this?)
> And on a related note as well, how to easy do unit testing of your own camel integrations
> - standard junit
> - using camel-core-tests
> - using camel-spring-tests
> - using spring unit tests with all its annotations etc
> - etc.

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