JDF-374 Fix to ensure bookings view is refreshed on delete

This required a server-side change to return HTTP 204 No Content responses instead of HTTP 200 OK. This is primarily due to a change in jQuery 1.9 that treats empty 200 OK responses as errors which cascaded to Backbone and eventually resulted in no updates to the view. The server-side change now results in a 204 response preventing this hidden failure.

demo/src/main/java/org/jboss/jdf/example/ticketmonster/rest/BookingService.java

@@ -71,7 +71,7 @@ public Response deleteAllBookings() {
     	for (Booking booking : bookings) {
     		deleteBooking(booking.getId());
     	}
-        return Response.ok().build();
+        return Response.noContent().build();
     }
 
     /**
@@ -105,7 +105,7 @@ public Response deleteBooking(@PathParam("id") Long id) {
                     booking.getPerformance(), sectionListEntry.getValue());
         }
         cancelledBookingEvent.fire(booking);
-        return Response.ok().build();
+        return Response.noContent().build();
     }
 
     /**