It's a framework for building RESTful web services.
It should be a good match for your app, because it will do all the
hard work of routing requests to action methods for you. And it has a
*beautiful* api.
Check it out:
https://jersey.dev.java.net/
/i
On May 8, 2009, at 2:47 AM, Survivant 00 wrote:
> never used jersey. Don't know what is for yet :(
>
> I'll look it.
>
>
> 2009/5/7 Igor Minar <iiminar_at_gmail.com>
> how about a jersey app running on grizzly webserver?
>
> sounds like an ideal combination to me + all the pieces already work
> together, you just need to create some jax-rs resources.
>
> /i
>
>
>
> On May 7, 2009, at 5:31 PM, Survivant 00 wrote:
>
> I'm looking for advice from the community. Here my usecase
>
> I'll have a httpserver that listen for http requests : nothign
> special here
>
> but thr requests will be for controlling a device (media server).
>
> Should I create a grizzly application that instanciate a
> GrizzlyWebserver and when I add manually ServletAdapter I pass a
> reference for the main application and when I receive requests, I
> dispatch them to the application ?
>
> or should I use a Grizzlywebserver standalone and call a service
> from the GWS ?
>
> oh ya.. I planned to add a web page to control the device too. Just
> not sure what is the best case schenario.
>
> I think of using the first one, but just want your advices on that.
>
> thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>