Sometimes properties files, configuration files, etc. need to be loaded at runtime. I found that using relative paths in a Java project can be frustrating (or impossible) and absolute paths should obviously be avoided for portability. I've had success with the approach of putting the file on the classpath and using a ClassLoader to load these resources at runtime. Here's an example to illustrate:

A number of changes were made to the identity service which is the first fully functional service in the APIUS framework. The focus of the identity service for the moment is still managing sessions on a remote session provisioner via a uniform RESTful interface, and the first concrete implementation is using OpenAM as the session provisioner.

There was some code clean-up including consolidation

There are a number of different HTTP methods, but the four that will likely be used the most in designing RESTful services are:

PUT

GET

POST

DELETE

It's easy to assume that each of these methods maps cleanly (one-to-one) to the CRUD operations common in programming (Create, Retrieve, Update, Delete) but that's not always the case for reasons that become clear when studying the HTTP RFC.

A