JBossDeveloper

Ole and Roman, thanks very much for these very useful comments. I'll come back to here once I get some movement on this.

"romankuzmik" wrote:
But here is another problem I have. I am not sure it should be addressed here, but conceptually it is also all about authentication.authorization. In our enterprise all services protected with WS-Security XML firewall layer. Depends on the privacy layer and other facts it varies from simple

<env:Header>
 <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext">
 <wsse:UsernameToken>
 <wsse:Username>???</wsse:Username>
 <wsse:Password>???</wsse:Password>
 </wsse:UsernameToken>
 </wsse:Security>
 </env:Header>

up to crazy combinations on the <wsse:Security/> headers plus SAML assertions plus XML Signatures plus XML encryptions. Probably it also should be handled in the pluggable way in SOAPClient?

OK.

I tried to get something sorted for this but have run into some issues, so it won't be in the MR3 release.

So what's coming is basically as I said above - a way of configuring a HttpClientFactory on the SOAPClient. I got BASIC Auth working fine, but have run into issues with https using a self-signed cert. HttpClient is supposed to work for this if you set the the "Easy" socket factory on the host configuration Protocol. Perhaps you can help me on this Ole - I might have a look at how you do this in soapUI too.

More on this later. Sorry it's not going to be in the MR3 release :-(

Hi Tom,

soapUI uses the commons-ssl proposal located at http://juliusdavies.ca/commons-ssl/, which contains an EasySSLProtocolSocketFactory that trusts "anything".. maybe you can use it too!?

regards!

/Ole
eviware.com

Thanks Ole. Since then, I actually figured out what was wrong and have fixed it. I was using EasySSLProtocolSocketFactory but was not registering it properly - I was setting it on the gost configuration and that was not working. Registering it using the static method on the Protocol class did the trick. I'll be checking this stuff in once the code freeze is finished.

Nope, it will not be in MR3. Sorry about that but I only got it done on Friday and wasn't able to check it in because of an issue I was having (outlined above).

This code is still not in place (codefreeze still in effect), but you can see how it works in the SOAPClient wiki page - goto the "HttpClient Configuration" section at the end.

OK, so support for configuring the connection (via the HttpClientFactory and Configurators) has been added now. It's in the trunk, so if you check out from SVN you'll get this now.

I've yet to tie this in properly with a quickstart. I'm waiting on the webservice_consumer quickstart to be added. I've tested it out on the webservice_bpel quickstart, but I don't wanna put it there because there's enough going on there already.

See the docs for this here on the wiki. See the section on "HttpClient Configuration".

If you've modified any files locally, revert to the repo reversion and try again. That file should be in conflict on your machine. The CI build machine is building this stuff fine, so the repo health is good. Also look at SoapUIClientService in the repo... no conflicts!

Hmmm. That looks like an svn merge issue. Did you get a fresh checkout?