[
https://issues.apache.org/jira/browse/CAMEL-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar KB updated CAMEL-5961:
-------------------------------
Description:
It would great to have a camel-dropwizard component. The details on dropwizard
can be found here:
* http://dropwizard.codahale.com/
* Github: https://github.com/codahale/dropwizard
Since Dropwizard works off a standard JVM (w/o the need of an app-server) and
same holds good for Camel, a camel-dropwizard integration would make AppServer
reduntant for serving RESTful webservices with Enterprise Integration
(Dropwizard internally uses a highly tuned variant of Jetty for HTTP).
Even a camel with Metrics could be a good idea to collect JVM metrics about
different routes. https://github.com/codahale/metrics
Any thoughts or comments?
was:
It would great to have a camel-dropwizard component. The details on dropwizard
can be found here:
* http://dropwizard.codahale.com/
* Github: https://github.com/codahale/dropwizard
Since Dropwizard works off a standard JVM (w/o the need of an app-server) and
same holds good for Camel, a camel-dropwizard integration would make AppServer
reduntant for serving RESTful webservices with Enterprise Integration
(Dropwizard internally uses a highly tuned variant of Jetty for HTTP).
Any thoughts or comments?
> camel-dropwizard component
> --------------------------
>
> Key: CAMEL-5961
> URL: https://issues.apache.org/jira/browse/CAMEL-5961
> Project: Camel
> Issue Type: Wish
> Affects Versions: 2.10.3
> Reporter: Ramkumar KB
>
> It would great to have a camel-dropwizard component. The details on
> dropwizard can be found here:
> * http://dropwizard.codahale.com/
> * Github: https://github.com/codahale/dropwizard
> Since Dropwizard works off a standard JVM (w/o the need of an app-server) and
> same holds good for Camel, a camel-dropwizard integration would make
> AppServer reduntant for serving RESTful webservices with Enterprise
> Integration (Dropwizard internally uses a highly tuned variant of Jetty for
> HTTP).
> Even a camel with Metrics could be a good idea to collect JVM metrics about
> different routes. https://github.com/codahale/metrics
> Any thoughts or comments?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira