Resources.

[Rod Widdowson]

FYI

I have just made the latest series of changes in this stream.  Apart from
now-deprecated code awaiting being moved, java-support only knows about a
single Interface (ShibbolethResource) which, as discussed previously, is
method-for-method compatible with the Spring one.  OpenSAML has been
modified to consume this and to use (in the tests cases) helper method:

ShibbolethResource  ShibbolethResourceHelper.as(Resource input);

The next stage is to port our SVN and HTTP resource implementations forward.


The SVN will (re)introduce a new dependency on SVNKIT.  This has a license
which I'd like someone to eyeball at http://svnkit.com/license.html.  It
looks OK, but I am no expert.  Also the version in maven central is quite
out of date so I am guessing that now is the chance for me to learn how to
populate our repository from theirs.

The HTTP port makes me very nervous given than I don't know my way around
HTTP as well as this work deserves, so I'm hoping that someone (*cough*
Brent *cough*) will be able to review it for me.

Both resources introduce an interesting question about configuration.  They
are just beans, so we can summon them up, call some setters and then inject
them wherever we want.  This only presents a problem in that we will need to
move some definitions from system to user configuration.

However a next step might be a desire to summon up resources via the
ResourceLoader interface (hence a configuration file might say
"svn+ssh://shibboleth.net/mumble").  Although the ResourceLoader but is
probably not difficult, it is not immediately obvious to me how to pass in
all the extra parameterization that these specialist resources require.

Rod