Hi *!
I have the same problem.
OK, assume I have a SSLSession object, then to get the searched information
is no
problem; but...
I have only the following few lines ( cut from a tutorial ):
Security.addProvider ( new com.sun.net.ssl.internal.ssl.Provider () );
System.setProperty (
Hi Scott,
I am sorted now - but thanks anyway.
My problem was the CLASSPATH was not set to pickup my Server-side Servlet.
Perhaps the info. in the FAQ should be changed from
The router URL you are using is incorrect or you have not started
the server. Basically the problem
If the problem was that your servlet was not in the CLASSPATH, the
message you were getting would not contain a stack dump from an
exception thrown from RPCRouterServlet.
In any case, glad to hear you are up and running.
Scott Nichol
- Original Message -
From: Jack Byrne [EMAIL
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
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
- 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?
Yes.
Is this the right packaging approach? Would you accept such a patch?
if (java.lang.version = 1.4)
{
s = new
Mike,
That approach does not work because it requires JDK 1.4 or later to
compile. The code both runs and compiles with JDK 1.2. With most JVMs,
I also believe it would fail at run-time on J2SE earlier than 1.4,
because the JVM will try to resolve external names when code within the
class is
There is no planned release date for the next version of Apache SOAP.
Scott Nichol
- Original Message -
From: Ehrlich, Dave [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, December 19, 2002 5:06 PM
Subject: RE: UnknownHostException not being caught
I replaced soap.jar from the
Excellent! I've tested with SSL and non-SSL connections, and it seems to
work perfectly. Will this be going into the nightly builds?
Thanks,
mike.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Mike,
Can you check again with SSL? That code path does *not* have a change,
so it should still take a longer time to timeout.
Scott Nichol
- Original Message -
From: Ladwig, Mike [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, December 20, 2002 10:39 AM
First off - thanks to Scott and others for responding to my recent posts...I've really
go the ball rolling on Apache SOAP/Resin Integration into my own web-app and life is
good. But, as is usual, I've yet another question (more questions).
A) Is WSDL relevant in messaging as opposed to RPC
You are right. I tested the timeout path only on the non-SSL test endpoint,
and on the SSL endpoint only verified that it wasn't broken by the change.
If you add the connect timeout code to the SSL path, I'll test it.
mike.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional
WSDL is relevant. In some ways, Apache SOAP messaging is a way to
provide doc/lit capabilities that WSDL specifies.
If you really want to get deeply into WSDL use, you should consider Axis
(http://xml.apache.org/axis/). If you just want to play with WSDL for
now, I still recommend grabbing Axis
FYI, this addresses the connect timeout question raised by Mike Ladwig.
Scott Nichol
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 20, 2002 4:40 PM
Subject: cvs commit: xml-soap/java/src/org/apache/soap/util/net
SocketUtils.java HTTPUtils.java
14 matches
Mail list logo
