Testing security in RESTful application with jersey and jbehave

Security concerns emerges naturally in applications because softwares have so many capabilities and we sure don’t want these features to be available to anyone. The important words in the above sentence areĀ features and anyone. Securing an application is often a matter of 2 concepts : identifying who should/should not access the system : aka Authentication.… Read More Testing security in RESTful application with jersey and jbehave

Testing error handling in RESTful application with jersey and jbehave

Hi reader, As far as I’m concerned I write tests mostly for one reason : deal with the non-nominal path because in most cases the nominal path is the easier one. They help me dealing with the question “What if the user/client doesn’t provide correct inputs how will my application behave ?“ RESTful applications are… Read More Testing error handling in RESTful application with jersey and jbehave

Testing REST content negotiation with jersey and jbehave

Hi everyone, When building RESTful services one very common concern is content negotiation. This feature allows a client (REST client), to specify its preferred response formats. The idea is “Dear server I’m sending you an application/x-www-form-urlencoded content but I’d rather get application/json results.” It also allows a server to specify its preferred request formats. Client… Read More Testing REST content negotiation with jersey and jbehave

REST client, CXF server : JAX-RS or SPRING-MVC ?

Hi reader, If you’ve read my previous article you know I had to provide a POC for a REST architecture. The target is : simple REST invocation with an even simpler implementation. The POC, a maven multi-project, includes : – core : entities, exceptions, service (jar packaging) – server : service implementation including a custom… Read More REST client, CXF server : JAX-RS or SPRING-MVC ?