views:

478

answers:

1

I have JAX-WS generate client proxys that need to connect using HTTPS. The certificate handling needs to be custom since we store the certs in a database instead.

I have a working version for the SUN JAXWS implementation, but now I need to have the same client code working in WebSphere 7.0.

Unfortunately the JAX-WS standard is a little weak in this regard. It is an implementation specific procedure on how to do this and in case of WebSphere I do not find a lot of information.

I noticed that Axis2 seems to be used but I find nothing usefull on how to set up the custom handshaking I have working in the SUN implementation.

A: 

Not even IBM can help me. So I just implemented my own JAX-WS -> SOAP conversion. That took 2 days and supports everything I need.

David Nouls