Raible Designs

I also played around with exposing RESTful Web Services - although - in my case project design is completely up to me and I don't have any existing dependencies - as it's a new project.

The server side with jersey was quite straightforward and I liked it. On the client side my first obstacle is using query parameters - here is a sample:

        ClientConfig config = new DefaultClientConfig();
        Client wsClient = Client.create(config);
        MultivaluedMapImpl queryParams = new MultivaluedMapImpl();
        queryParams.add("view", "detail");
        WebResource req = wsClient.resource("http://localhost:8080/TestWebService/resources/generic");
        ClientResponse response = req.path(item).accept("application/json").get(ClientResponse.class);
        return response.getEntity(String.class);

I couldn't get the queryParams added to the request and further I really dislike the approach

req.path(item).accept("application/json").blablabla().blablal().get(ClientResponse.class);

Why not something like

req.setPath(item);
req.setAccept("application/json");
req.setQueryParams(queryParams);
ClientResponse response = req.get(ClientResponse.class);

Posted by Martin Wildam on August 28, 2009 at 01:55 AM MDT #

I've finished a RESTful project using Glassfish(Jersey) , Apache HttpClient, XStream for domain object to/from XML and Swing based client.

It was a quite interesting experience.

Posted by Kenneth on August 28, 2009 at 04:40 AM MDT #

Hi. I decided to give Resteasy a try. Being a JBoss subproject that offers a straight forward spring integration and it's quite well documented.

I am not sure, whether endpoints can be declared as xml. The web service endpoints are annotated:

   @GET
    @Produces({"application/xml", "application/json"})
    @Path("{id}")
    public Response getAd(@PathParam("id") Long id,
            @QueryParam("fields") String aliasCSVs) { ... }

So far I came across two major issues with this framework.

• Resteasy does not honor the the requested encoding.
• I stumbled across a json namespace issue, too.

Posted by Lars Behnke on September 07, 2009 at 02:27 AM MDT #

Posted by Ken Brown on November 12, 2009 at 10:04 AM MST #

Posted by Matt Raible on November 12, 2009 at 10:41 AM MST #

Posted by Bill Burke on November 12, 2009 at 11:09 AM MST #

Matt, any reason you didn't include RESTEasy in your analysis?

No reason in particular, except that I was originally trying to use Enunciate and it didn't have RESTEasy support.

Posted by Matt Raible on November 12, 2009 at 11:33 AM MST #

Could you please let me know if you know any good architecture that support

EXTJS front-end

and a

SOAP-based WS in the backend ?

I'm required to write a brand-new UI using Ext JS that would calls an existing SOAP WS .

I have tried EXT JS with REST before, and it's easily done. But given an existing SOAP layer to plug into EXT JS , I don't have a good architecture in hands.

Please let me know .
Thank you

Posted by tho dinh on November 13, 2009 at 12:45 PM MST #