Build RESTful web services with Java technology

Post by moondowner » Wed, Aug 15, 2012, 8:43 AM UTC

mbell wrote: post #19

edwinnathaniel wrote: post #15

Earlier quoted context omitted.

JPA does have some gotchas and the learning curve is a little bit steep (not too steep, but just a wee bit). You do need to know how JPA works internally a little bit (e.g.: EntityManager actually cache your objects unless you tell it specifically to "flush").

My biggest problems with JPA: 1) CriteriaBuilder API is the worst API I've ever seen. I've never seen an API that turns a simple task into more lines of code than this monstrosity. I can't imagine many people use this thing, instead they use JPQL losing type safety in the process. 2) JPQL is still wildly verbose and very difficult to intertwine with native SQL. As an example try to generate something like "SELECT * F…

Post by bradgessler » Wed, Aug 15, 2012, 10:05 AM UTC

Post by ilcavero » Wed, Aug 15, 2012, 11:46 AM UTC

mbell wrote: post #2

Building REST services with JAX-RS is truly pretty smooth and quick (I've been using Jersey not Wink though). One thing I don't ever recommend is using JPA based libraries (Hibernate, EclipseLink, whatever). Run screaming away from that spec as fast as you possibly can. There are much better options for ORMs in Java that don't have the session management headache and endless string of gotchas that is JPA. Ebean is my…

Post by facorreia » Wed, Aug 15, 2012, 12:37 PM UTC

kooshball wrote: post #17

rohshall wrote: post #4

Earlier quoted context omitted.

Thanks a lot for the pointers. I have been looking for a good java framework to learn. I will be more than happy to settle with this 90% you quoted. They look simple enough to understand in a couple of days without wrestling with tons of XML config files.

If you're looking to write a backend service using Java, I would take a serious look at dropwizard http://dropwizard.codahale.com/ The get started page is not that long, and you should be able to kill it in a few hours. At the minimum you get http requests routed to methods and restful json parsed for you automatically. If you want, you can add optional configuration, metrics, healthcheck, logging, db access, views e…

Post by rauar » Wed, Aug 15, 2012, 6:07 PM UTC

moondowner wrote: post #20

rauar wrote: post #16

Earlier quoted context omitted.

I prefer plain files instead of annotations. Just wish the non-readability of XML would go away with less bloated format (which other frameworks did with JSON).

Fair enough argument :) Though, now that I've gotten into the annotation way I like it the most.