BTW,
this is the stack trace we are getting,
org.apache.axis2.AxisFault: Unconnected sockets not implemented;
nested exception is:
java.net.SocketException: Unconnected sockets not implemented; nested exception is:
org.apache.axis2.AxisFault: Unconnected sockets not implemented; nested exception is:
java.net.SocketException: Unconnected sockets not implemented
java.net.SocketException: Unconnected sockets not implemented; nested exception is:
org.apache.axis2.AxisFault: Unconnected sockets not implemented; nested exception is:
java.net.SocketException: Unconnected sockets not implemented
-----Original Message-----
From: Dale Herrig
Sent: Sunday, September 17, 2006 9:06 AM
To: [EMAIL PROTECTED] Apache. Org (E-mail)
Subject: WS-Security and HTTPS compatibilityHi,We implemented WS-Security meaning we digital sign and digital encrypted the SOAP body. This works very well and as expected. The next step was to have our Server and our Clients run over HTTPS (SSL). At this point we ran into lots and lots of problems. Are WS-Security and HTTPS compatible with each other. If so, are their any special requirements that the server and client must follow, could you point me to any document that might be useful in this area.Thanks,Dale
