You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/05/15 20:08:48 UTC
[jira] Resolved: (CAMEL-1613) Provide a CamelServer for
testing/demo/small apps purposes
[ https://issues.apache.org/activemq/browse/CAMEL-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1613.
--------------------------------
Fix Version/s: (was: Future)
Resolution: Won't Fix
> Provide a CamelServer for testing/demo/small apps purposes
> ----------------------------------------------------------
>
> Key: CAMEL-1613
> URL: https://issues.apache.org/activemq/browse/CAMEL-1613
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M2
> Environment: Any
> Reporter: Bruno Borges
>
> It's common to code a "CamelStartup" class to call through maven-camel-plugin or directly from the IDE.
> But now all threads inside CamelContext are daemon, causing the VM to shutdown right after the main() method is called, even if the Context is still starting.
> The Main class from camel-spring should have a version on camel-core for projects not Spring-related.
> The Maven plugin should then check the configured class to see if it is Spring based (org.apache.camel.spring.Main) or a standalone application (org.apache.camel.server.CamelServer).
> <plugin>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-maven-plugin</artifactId>
> <configuration>
> <mainClass>org.apache.camel.twitter.demo.CamelStartup</mainClass>
> </configuration>
> </plugin>
> public class CamelStartup {
> public static void main(String[] args) {
> CamelServer server = new CamelServer();
> server.addContext(new MyContext());
> server.start();
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.