This is related to issue 133 but generalized to any transport mechanism and
extended to allow use of the API against multiple services concurrently.
The client API currently has a static ResourceFactory which is limiting if you
want to use the API against multiple services (it seems like transport /
authentication settings should be factory scoped, though this may be a
misunderstanding on my part).
The current HTTP client sets the JDK global defaults for the Authenticator and
the SSLSocketFactory which may be too restrictive for some usages.
There is currently no way to add in functionality such as including the SOAP 1.2
action parameter in the Content-Type header.