Re: 答复: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Prajwal Tuladhar
+1 for DW On Tue, Feb 23, 2016 at 9:13 PM, John Fang wrote: > +1 for DropWizard > > -邮件原件- > 发件人: Hugo Da Cruz Louro [mailto:hlo...@hortonworks.com] > 发送时间: 2016年2月24日 6:36 > 收件人: dev@storm.apache.org > 主题: Re: [DISCUSS] Java REST Framework adoption > >

答复: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread John Fang
+1 for DropWizard -邮件原件- 发件人: Hugo Da Cruz Louro [mailto:hlo...@hortonworks.com] 发送时间: 2016年2月24日 6:36 收件人: dev@storm.apache.org 主题: Re: [DISCUSS] Java REST Framework adoption I also vote on DropWizard > On Feb 23, 2016, at 2:29 PM, Parth Brahmbhatt > wrote: > > +1 o

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread P. Taylor Goetz
+1 for Dropwizard as well... It includes metrics, which we're already using elsewhere. And I'm all for dependency reuse. -Taylor > On Feb 23, 2016, at 5:29 PM, Parth Brahmbhatt > wrote: > > +1 on DropWizard. > >> On 2/23/16, 2:02 PM, "Harsha" wrote: >> >> -1 on spring boot or anything rel

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Hugo Da Cruz Louro
I also vote on DropWizard > On Feb 23, 2016, at 2:29 PM, Parth Brahmbhatt > wrote: > > +1 on DropWizard. > > On 2/23/16, 2:02 PM, "Harsha" wrote: > >> -1 on spring boot or anything related to spring. >> This api is intended to be very simple powering UI and any rest clients >> interested in

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Parth Brahmbhatt
+1 on DropWizard. On 2/23/16, 2:02 PM, "Harsha" wrote: >-1 on spring boot or anything related to spring. >This api is intended to be very simple powering UI and any rest clients >interested in grabbing the metrics from the same api as UI does. > >Jersey is good and dropwizard (http://www.dropwi

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Harsha
-1 on spring boot or anything related to spring. This api is intended to be very simple powering UI and any rest clients interested in grabbing the metrics from the same api as UI does. Jersey is good and dropwizard (http://www.dropwizard.io/0.9.2/docs/) has been a way to go for java REST api of

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Ravi Sharma
spring boot + Ravi On Tue, Feb 23, 2016 at 3:16 PM, Ankur Garg wrote: > How about using Spring Boot & Jersey for writing this . Spring Boot will > give us packaged jar which once executed will bring up its own embedded > server (Jetty or Tomcat or some other ) . Although Spring Boot has some

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Ankur Garg
How about using Spring Boot & Jersey for writing this . Spring Boot will give us packaged jar which once executed will bring up its own embedded server (Jetty or Tomcat or some other ) . Although Spring Boot has some disadvantages as well , but worth investigating this option too . Any thoughts

Re: [DISCUSS] Java REST Framework adoption

2016-02-23 Thread Bobby Evans
Yes, we need to pick something.  I have used Jersey in the past and I think it is fairly decent.  I have never used RESTEasy, but it is more or less the same API, so either one is fine with me, but Jersey is my vote just because of experience. You should keep in mind that we are currently on a

[DISCUSS] Java REST Framework adoption

2016-02-23 Thread 伍翀(云邪)
Hi all, I’m planning to move UI/REST service and logviewer to Java, which means that we need to pick some alternatives for ring and hiccup.  So the first thing is to pick up a REST framework. For the REST APIs, I think Jersey is a good choice (RESTEasy is fine too). It’s easy to develop and good