Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #35986

Re: generic rest-api

Show all headers | View raw

Hello,

I have tested Jersey/Jackson and this is a good choice for me. In my case I need POST / GET and hopefully PUT and DELETE, but at the moment POST / GET are enough

Thanks for both answers.

Am Dienstag, 22. November 2016 21:46:18 UTC+1 schrieb Sebastian:
> Am 22.11.2016 um 01:59 schrieb Arne Vajhøj:
> > On 11/21/2016 7:08 PM, Philipp Kraus wrote:
> >> I'm writing a framework which should be also accessable with a
> >> webservice. At the moment I'm using Jetty for the server.
> >
> >> Is there any componente or framework to create a structure like this
> >> and is also portable to Tomcat, Jetty and Glassfish?
> >
> > Most likely any solution will be portable among any Java web container.
> >
> >>                                                        I have got
> >> a set of objects and each object should be defined as a webservice
> >> with a REST-API which returns the object as a JSON structure.
> >>
> >> I need a call like http://server/"any path"/object_identifier/state
> >> which returns the current state of the object (I can get these
> >> information by calling a method). And also I need for each method in
> >> the object a call like http://server/"any
> >> path"/object_identifier/methodname The best case should be an
> >> automatically generation of all this URLs.
> >>
> >>                                                    I'm knowing
> >> Jersy, but I think I need some wrapper code around to do this.
> >
> > The standard way is using JAX-RS.
> >
> > I believe that Spring has its own non-standard thing.
> >
> > http://server/"any path"/object_identifier/state is easy
> > as it is just a normal RESTful GET request.
> >
> > http://server/"any path"/object_identifier/methodname is
> > tricky because it is not RESTful but RPC style.
> >
> > RESTful only have resources and GET, POST, PUT and DELETE.
> >
> > Arne
> >
> Yes, you should use a JAX-RS implementation. There are many of them, 
> however. These links (one for Apache CXF, the other for Jersey/Jackson) 
> were useful to me:
> 
> https://www.nabisoft.com/tutorials/java-ee/producing-and-consuming-json-or-xml-in-java-rest-services-with-jersey-and-jackson
> 
> https://idodevjobs.wordpress.com/2014/08/30/develop-a-simple-restful-webservices-using-apache-cxf-and-spring-framework/
> 
> You pays your money and you takes your choice.
> --Sebastian

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

generic rest-api Philipp Kraus <philipp.kraus.flashpixx@gmail.com> - 2016-11-21 16:08 -0800
  Re: generic rest-api Arne Vajhøj <arne@vajhoej.dk> - 2016-11-21 19:59 -0500
    Re: generic rest-api Sebastian <nowhere@nirvana.org> - 2016-11-22 21:46 +0100
      Re: generic rest-api Philipp Kraus <philipp.kraus.flashpixx@gmail.com> - 2016-11-29 00:18 -0800

csiph-web