+1 for DropWizard -----邮件原件----- 发件人: Hugo Da Cruz Louro [mailto:[email protected]] 发送时间: 2016年2月24日 6:36 收件人: [email protected] 主题: Re: [DISCUSS] Java REST Framework adoption
I also vote on DropWizard > On Feb 23, 2016, at 2:29 PM, Parth Brahmbhatt <[email protected]> > wrote: > > +1 on DropWizard. > > On 2/23/16, 2:02 PM, "Harsha" <[email protected]> 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.dropwizard.io/0.9.2/docs/) >> has been a way to go for java REST api offlate. Underneath it uses >> jersey and one can run jetty server as well which is what we've as >> the UI and logviewer server. >> >> >> -Harsha >> >> On Tue, Feb 23, 2016, at 08:23 AM, Ravi Sharma wrote: >>> spring boot + >>> >>> Ravi >>> >>> On Tue, Feb 23, 2016 at 3:16 PM, Ankur Garg <[email protected]> >>> 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 >>>> disadvantages as well , but worth investigating this option too . >>>> >>>> >>>> Any thoughts?? >>>> >>>> Thanks >>>> Ankur >>>> >>>> On Tue, Feb 23, 2016 at 8:20 PM, Bobby Evans >>> <[email protected]> >>>> wrote: >>>> >>>>> 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 very old >>>>> version >>> of >>>>> jetty, and I am not sure if newer libraries will work with it. >>>>> But >>> also >>>>> the old versions of ring and hiccup that we use don't support >>>>> newer >>> jetty >>>>> versions either. >>>>> >>>>> I personally think that now would be a good time to separate out >>> the UI >>>>> into a separate package + classpath. This would allow us to >>> package the >>>> UI >>>>> as both a war with embedded jetty as a default option to run it; >>> start >>>> from >>>>> scratch with up to date versions of Jetty, Jersey/RESTEasy, and >>> JAXB; and >>>>> upgrade the different servers/components one at a time instead of >>> all at >>>>> once. The DRPC server also uses the embedded jetty and exposes a >>> REST >>>>> interface, and that is going to be a harder one to tease out so it >>> should >>>>> probably be the last one to go. >>>>> - Bobby >>>>> >>>>> On Tuesday, February 23, 2016 3:40 AM, 伍翀(云邪) < >>>>> [email protected]> wrote: >>>>> >>>>> >>>>> 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 performance. >>>>> Now logviewer use hiccup to return HTML we build ourselves, but >>> it’s hard >>>>> to debug and maintain. So in my opinion, it’s better to replace it >>> with >>>>> static HTML + REST like regular UI. >>>>> Please let me know what you think. >>>>> – Jark Wu >>>>> >>>>> >>>>> >>>> >> >
