camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aldrin Leal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5961) camel-dropwizard component
Date Sat, 04 Jan 2014 23:31:51 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862445#comment-13862445
] 

Aldrin Leal commented on CAMEL-5961:
------------------------------------

Not sure how Dropwizard would integrate with Camel (since Dropwizard is based on Guice, and
Camel's Guice Support is, as we say in Brazil, "mais feio que bater na mãe"), but here's
what I've made using Spring instead, to measure Exchange Events of interest

https://gist.github.com/aldrinleal/8262171

Note it depends on a kludge to tag those exchanges. In my routes, I define the CamelMetricSuffix
Exchange Property (as shown in the gist)

If there's enough interest to turn this into a Camel Module, just let me know. I do have a
CLA ready.

Thanks



> camel-dropwizard component
> --------------------------
>
>                 Key: CAMEL-5961
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5961
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.10.3
>            Reporter: Ramkumar KB
>             Fix For: Future
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message