>Apache SOAP runs on J2SE 1.2 and later. As such, it cannot use >Socket#connect, which was added in J2SE 1.4, I believe.
You're correct. Unfortunately, this 100 sec timeout is a big problem for me; I need to find a workaround. - I'm not knowledgable about packaging binary jars; is there a way to conditionalize the HTTPUtils code so that on JDK1.4 and above the not-broken socket API is used? - Is there a way to override the 100 sec timeout through a system property? - Is there a way to interrupt the socket constructor? Last resort for me is to create a private SOAP lib with the problem fixed using the 1.4 socket calls, but I hate doing stuff like that. >Scott Nichol mike. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
