+1 Jersey/JSON/REST, but I would suggest you ensure you use Jackson instead of jettison for your JSON parsing library (jettison is default, at least on glassfish). Mostly, you'll be able to just use straight JAX-RS without having to use Jackson directly - but jackson does two things I find really important over jettison: returns dates in ISO format, renders an empty collection/array as an empty JSON array instead of null/renders a single element collection as a JSON array vs an object.
S On Fri, Mar 16, 2012 at 6:35 PM, clay <claytonw...@gmail.com> wrote: > I'd add +1 vote to a Jersey + REST + JSON solution. > > I did a fair amount of this work. Jersey didn't do very much, but provided > a simple, clean, elegant web services framework that did everything we > needed. It was perfect, yet minimalistic. For a server, we used embedded > Jetty for development and Tomcat for production, which worked well. > > I did my Jersey work in Java, but if I had to start over without legacy > considerations, I'd use Scala instead (but keep Jersey). > > On Friday, March 16, 2012 4:25:24 AM UTC-5, raks wrote: >> >> Hi, >> >> wanted the wisdom of the group to help me out. >> >> My current project is essentially a platform providing web services to >> a number of clients. >> >> We've developed the web services by using Grails as it was considered >> a very quick way to get things going. >> >> Grails has been a positive experience from a development point of view >> but there are a number of disadvantages which are now prompting a >> rethink: >> >> Grails' sweet spot is creating a web application (rather than web >> services) to do CRUD. >> >> Our platform is not about typical CRUD. We do not have a html >> front-end for example. Or a relational db. We use Mongodb. >> >> We are also concerned about the runtime performance of Grails as well >> as how long it takes to startup in Jetty. >> >> So can anyone suggest an alternative? Performance and load are >> important. Being able to expose web services easily from Java is also >> important. >> >> I was thinking using Tomcat + Spring, mainly because its a stack I >> know and Tomcat can handle a huge load and I can pick and choose the >> bits of Spring I need. I would consider something lighter weight but I >> really don't want to muck around with web.xml files and the usual >> standard java web app crap (which Grails does a fantastic job of >> abstracting away). >> >> Any other ideas? >> >> Thanks >> >> Rakesh >> >> -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/javaposse/-/z82cQnuIWgIJ. > > To post to this group, send email to javaposse@googlegroups.com. > To unsubscribe from this group, send email to > javaposse+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- *...Seggendo in piuma in fama non si vien, né sotto coltre, sanza la qual chi sua vita consuma cotal vestigo in terra di sé lascia qual fummo in aere ed in acqua la schiuma.* -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
