It was rough. I'm still hearing a constant creeking noise in my ears. Also my writing skills are greatly hit and damadged since I've been hitting backspace too many times for last two lines. Plus my roomate is listening Led Zeppelin right now. I somehow have the feelin', "yeah baby give me the feelin", that I'll turn all this noise off. Hats off to mr. Hell, a little bit crude, I once felt Fisherspooner and other folks but still, he's OK. Or maybe it's the second hand smoke, who knows. In the end I went back home with my pal Dora, and we ate 2 sandwiches, and to hell with diet! I'm off to sleep, tomorrow it's either JSP or SQL, all day long. (Unless I have a hangover)
Relaxing SSL validation for JaxWS
I've recently had the need to access a web service developed in .Net and signed with a self signed certificate. I've decided to use the JaxWS and the Metro stack to develop the client and run it on Java6. As a plus, the service was protected with username and password. The service was exposed on an IP address and I repetedly had problems in establishing a connection. In the end, thanks to this article, it was obvious that the certificate was not created with the alternative name attribute but it was not an option to change the certificate as the web service was already used by other consumers (.net clients don't suffer by this issue). So, on my quest to relax the validation, I've found out this article and code snippet, which did not compile at first (I guess package names were changed in JDK6) so I've did some trivial refactoring and now, after invoking the static methods in the client code, the SSL connection gets validated with no problems. Hope it helps and th...
Comments