Uhg... This is definitely a bug.
It SHOULD just be calling off to the WSDLManager to get the wsdl with the
original URL. That would allow catalogs to work as well as the HTTPS conduit
settings and such (and thus the TLS certs).
Please log a bug (and a patch would be nice). Probably just:
WSDLManager m = bus.getExtension(WSDLManager.class);
m.getDefinition(url);
or similar.
Dan
On Fri July 10 2009 2:59:28 pm Allan Felipe Silva wrote:
> Hi,
>
> I am trying to use dynamic clients with https connection, without the JVM
> properties.
>
> Without this :
> System.setProperty("javax.net.ssl.keyStore", "blahblahblah");
> System.setProperty("javax.net.ssl.keyStorePassword","blahblahblahblah");
>
>
> Why I need this ?
> To install a new certificate on my jssecacerts and start to use
> immediately, with this VM parameters I need to reset my VM everytime I
> install a new certificate. (with muthual authentication scenario)
>
> The method tryFileSystem in org.apache.cxf.resource.URIResolver only gets a
> HttpUrlConnection.
>
> Changing this method the problem is solved, with a HttpsUrlConnection
> everything works fine without a VM property.
>
> Is possible this class use a TLSClientParameters in a near future ?
>
> Can I implement this and send to you ? or there is another solution ?
>
> Thank you
>
> Allan Felipe Santos
> Joinville SC Brazil
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
