True, but we don't move between impls that often, do we? :-)

*Bruno Borges*
(11) 99564-9058
*www.brunoborges.com*



On Fri, Sep 21, 2012 at 4:11 PM, Martin Grigorov <[email protected]>wrote:

> On Fri, Sep 21, 2012 at 8:58 PM, Bruno Borges <[email protected]>
> wrote:
> > Jersey is really good, but you also should consider using the spec
> JAX-RS.
> > Why not?
>
> Because specs are boring and the compatibility between different impls
> is not as they claim it to be.
>
> >
> >
> > *Bruno Borges*
> > (11) 99564-9058
> > *www.brunoborges.com*
> >
> >
> >
> > On Thu, Sep 20, 2012 at 5:00 PM, Dan Alvizu <[email protected]
> >wrote:
> >
> >> I've used wicket-rest before - it got the job done, but I couldn't use
> it
> >> for wicket 1.5.
> >>
> >> Since then I've moved my rest services to Jersey - I highly recommend
> using
> >> that if you can:
> >>
> >> http://jersey.java.net/
> >>
> >> -Dan
> >>
> >> On Thu, Sep 20, 2012 at 1:21 PM, Josh Kamau <[email protected]>
> wrote:
> >>
> >> > Good idea...
> >> >
> >> > I would like to use JSON though...
> >> >
> >> > Josh.
> >> >
> >> > On Thu, Sep 20, 2012 at 10:14 PM, Ernesto Reinaldo Barreiro <
> >> > [email protected]> wrote:
> >> >
> >> > > I have implemented "rest like services" by mounting pages and using
> >> them
> >> > to
> >> > > generate XML content instead of HTML.
> >> > >
> >> > > On Thu, Sep 20, 2012 at 7:54 PM, Josh Kamau <[email protected]>
> >> > wrote:
> >> > >
> >> > > > Hi Guys;
> >> > > >
> >> > > > Is there a way(a sub project may be..) of exposing a wicket web
> app
> >> as
> >> > a
> >> > > > REST API.... ?
> >> > > >
> >> > > >
> >> > > > Josh.
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Regards - Ernesto Reinaldo Barreiro
> >> > > Antilia Soft
> >> > > http://antiliasoft.com
> >> > >
> >> >
> >>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to