SSL transport support and the Options class

[Darrel Drake <EB...@jp.ibm.com>]

Hello all. Axis can now work over SSL.

(See attached file: HTTPDispatchHandler.java)(See attached file:
Options.java)

I just added a few lines to HTTPDispatchHandler (7 to be exact) and wrapped
some small snippet of code into an if statement. I can make the JSSE calls
reflective momentarily, and I will. By the way, since it only calls on
classes in the javax.net.ssl package, it will run with either Sun or IBM
JSSE in the classpath / ext directory.

At first I got the very strange and cryptic "socket write error" the source
of which it took me quite a while to discover. The problem was that
Options.getURL() was directly overwriting the "https" part of my URL with
"http"(I had used the "-l" option to set the servlet URL). There was one
other logical problem with the code in that method, namely it didn't handle
an omitted port number correctly if you didn't specify it in the "-l"
option (it puts a -1 in the output string). So I took the liberty of
correcting that mistake. However, I don't quite see the need for the
existence of this Options class. It seems that parsing command line options
is best left to the actual SOAP client program, as it was in Apache SOAP
2.1. If the SOAP platform is going to look for options, it should look at
System properties, like most Java toolkits. Can someone help me understand
why it was done this way?

Darrell Drake*
IBM Japan, TRL
+81-46-215-4175
EB92401@jp.ibm.com
* - Notes ID has a misspelling of my name