link up groovy script to spring backing bean for getting content
be a bit forgiving on inbound paths (specifically //)
separate looking up a node ref via path, this is slow but re-usable
dynamically determine the alfresco ticket
layering the code
layering the code
content exists and code clean up
layering the code, pushing repository down and making it a much more simple interface.  content services is a more complex, composite service
layering the code, pushing repository down and making it a much more simple interface.  content services is a more complex, composite service
working getItem, not all properties supported
removed some dependencies on alfresco repository layer
make version history work
support revert
fully functional revert
code cleanup
remove item terminology from repository interface
moved all the methods I don't want the repository to know about to a "dirty" class that implements the full "dirty" interface
a little code clean up
getItemsTree
getItemsTree
it's a tree, so it needs a root
a little better but still not right