I'm not quite sure fixing that jira will solve this particular issue. It seems to me that CXF has trouble connecting to anything HTTP once it has been configured to use HTTPS.
2007/11/1, Willem Jiang <[EMAIL PROTECTED]>: > Hi Christian, > > I think we could achieve you goal by letting service that CXF published > the WSDL with user defined , so you could add what you want https or > http protocol string on the address or the xsd including part. > > Here is a JIRA[1] of trace it, if you have time to write a patch , I can > give your some points from my view. > [1]https://issues.apache.org/jira/browse/CXF-341 > > Willem. > > Christian Vest Hansen wrote: > > We're planning on exposing a number of web services through HTTPS, > > however, many of the WSDLs will refer to and import schema files that > > we have stored in a central repository - and this repository is > > accessed through ordinary HTTP. > > > > In other words, our clients access a WSDL through HTTPS - this WSDL > > has references to a schema that the client has to access through plain > > HTTP. > > > > Will this cause any problems with HTTPConduits and other > > configurations that clients will have in order to access the otherwise > > HTTPS enabled web service? > > > > > > > > > -- Venlig hilsen / Kind regards, Christian Vest Hansen.
