Unfortunately, this is a known issue. :-( Basically, for the SOAP communication, the http:conduit bean things in the config are used to pick up authentication things, ssl certs, etc... so a proper secure connection can be made to protect the data.
Unfortunately, the WSDL retrieval part doesn't use the conduits. It just uses a plain old ordinary "new URL(address).openConnection().getInputStream()" type thing. Dan On Thursday 06 March 2008, xbranko wrote: > Yes it does. I was able to use it, by using a locally cached copy (to > avoid the authentication problem). Given that the auto generated code > uses class javax.xml.ws.Service, during object instantiation the > problem is there (see my answers to previous posts). > > It seems that for authenticated web services, another approach is > needed. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
