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
