Port AACLI command line from V2

Batch files done. As of Java 6 or possibly 5, we can use wildcards for the classpath. When I tried to build a classpath with all the jars on it, it kept failing with a command line limit, but rather than debug, I just switched to a wildcard. I suspect we can dump the cpappend trick now.

TBD: Windows batch scripts to run the CLI tools.

Summary of work:

http://marc.info/?l=shibboleth-dev&m=141212754716227&w=2

Resuming this work (after 18 months! wow), creating a REST interface to a flow that resolves attributes and then optionally encodes attributes to a specified protocol.

Flow skeleton is done, a message decoder is built, and a dispatch table will route the flow to encoding steps that will build SAML assertions. Final step will be a view that either dumps assertions, or can generate a simple JSON attribute dump of the IdPAttributes.

The eventual AACLI tool will be a Java shell that just calls the flow as an HTTP GET and echoes the results. Can simulate the existing command line options.

Checked in a shell that can handle command line, loads a Spring container with a new version of internal.xml with custom logging and control over OpenSAML parser.