Although the following involves some kind of code changes, I doubt anything should be amended for the trunk.
It happens that I'm using the package on a Weblogic 9.2 application server, and when I use the new version of JML, something's wrong such that login seems incomplete -- it "stopped" after the authentication challenge is received.
I changed the source a bit such that no errors will be covered up, and I found that a ClassCastException occured in the handling method of IncomingUSR class. After going through the Javadocs, I found that Weblogic's HttpsConnection class hierarchy is a bit different from that of J2EE. I changed all HttpsConnection reference to HttpConnection, and everything becomes ok.
I hope it's just a special issue on a special platform.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although the following involves some kind of code changes, I doubt anything should be amended for the trunk.
It happens that I'm using the package on a Weblogic 9.2 application server, and when I use the new version of JML, something's wrong such that login seems incomplete -- it "stopped" after the authentication challenge is received.
I changed the source a bit such that no errors will be covered up, and I found that a ClassCastException occured in the handling method of IncomingUSR class. After going through the Javadocs, I found that Weblogic's HttpsConnection class hierarchy is a bit different from that of J2EE. I changed all HttpsConnection reference to HttpConnection, and everything becomes ok.
I hope it's just a special issue on a special platform.
In the above article, HttpsConnection should be HttpsURLConnection, and HttpConnection should be HttpURLConnection.