Configured Spring Securities default implementation of Access Control
Lists.

To use:
 -import the tables in the mysql dir.
 -make changes to the context.xml and aclConfig.xml so that data sources
will connect to the correct DB.
 -only one service method is currently being access controlled.  A @get
request to /users will invoke the postFilter.  Only the users which the
logged in user has read privilages for will be returned in the json.
 
 
 For additional information about this implementation please see
http://krams915.blogspot.com/2011/01/spring-security-3-full-acl-tutorial.html
I will update the readme in a bit.  Basically now the ACL is fully
functional and you can add and (soon delete) and edit users and their
permissions will be maintained automatically. A generic Acl controller
was added to be used by future services to handle all acl related
maintanence.
Updated readme to include instructions on how to use new functionality.

New features:

-Creating a user automatically creates an ACL for the user along with
ACEs that allow a user read, write, and delete permission for thier own
User object.

-Deleting a user automatically removes any ACEs and Authorities
associated with that user. It also sets any ACLs owned by the deleted
user to have owner_sid as NULL.

-GenericAclController is available for any new resource managing
services to use.  It contains methods for maintaining ACLs and ACEs of
any object that implements interface IAclObject.

Changes:
-deleteUser now requires that the request contain a JSON of the user to
be deleted and the JSON must include id set to not null.

-reworked the mysql tables so that they handle user deletion gracefully
Merge remote-tracking branch 'origin/master' into Core-ACL

Conflicts:
	.classpath
	pom.xml