buildscientist / vrrdl-ws Goto Github PK

Authenticated users should be allowed to delete debris.

Currently the /proximity resources uses a radius with a unit of measure of kilometers. VRRDL-WS users should be able to select the unit of measure they want to use including:

1. Meters
2. Kilometers
3. Miles
4. Yards
5. Feet

this UUID will be used to identify the debris and will be used for REST operation. Hence the value should be return when user PUT debris, GET debris, and user will pass as param for DELETE debris

Data is currently persisted to an in-memory hashtable implemented as a Singleton. Since memory is volatile if the service is stopped or the hardware it resides on is interrupted all data is lost.

Currently when debris is deleted it is purged from the database. Instead of purging the debris from the DB - it should be marked as removed.

When a client attempts to retrieve the debris a JSON response as follows should be returned:

{"latitude":"25.02321","longitude":"-150.02343","status":"removed","dateRemoved":"2013-02-19T06:38:20.185+0000"}

The other alternative is to return an HTTP status code of 410 (Gone). This is a bit more RESTful and doesn't require clients to parse JSON.

In memory data persistence is currently non configurable. Use a configuration library to toggle whether or not in memory data persistance is activated.

The web service is currently packaged as a WAR but still needs to be deployed in a servlet container. Add an embedded servlet container to the package such that the WAR can be run standalone.

The RESTful web service does not contain any API tests that test each RESTful endpoint.

The web service should implement a metrics library similar to Metrics such that performance metrics about the web service can be collected.

All exceptions and request/response headers are logged to STDOUT. The web service should use a logging library like SL4J to allow logs to be appended to any configured output stream.