The catalog manager might help, but, really, Glen's suggestion will lead to much faster performance.
On Sun, Mar 23, 2008 at 1:47 AM, Glen Mazza <[EMAIL PROTECTED]> wrote: > I'm not sure, but I think you're trying to create a dynamic client which > is unfortunately not working for you. Hopefully someone else can answer > your specific question on this, but in the meantime, you might wish to > try the more traditional route of getting the WSDL and XSD's on your > machine locally, running wsdl2java and then coding your SOAP client > using the wsdl2java artifacts generated, similar to here[1]. Once done, > any missing XSD's from the server should no longer be a concern for you. > > HTH, > Glen > > [1] http://www.jroller.com/gmazza/date/20070929 > > > Am Samstag, den 22.03.2008, 16:28 -0700 schrieb Kalle Korhonen: > > Hello cxfers, > > > > I'm trying to consume some web service with jaxws/cxf. I use > Service.create(new > > URL("http://some.server/service?wsdl";), SERVICE_NAME). The service's > wsdl > > imports xsd with a relative schemaLocation (e.g xsd:import > > namespace="servicens" schemaLocation="servicens.xsd") , but the .xsds > are > > not available through the server (from http://some.server/servicens.xsd), > so > > constructing the service (client) fails with FileNotFoundException. I > have > > the xsds but I don't know how to tell cxf's servicefactory where the > xsds > > are located. I've seen quite a few other threads on the list related to > > resolving references to xsds but the service is not mine so I cannot > change > > the references or make the xsds available on the server. If I point to a > > local wsdl, the service factory doesn't even try to resolve the schemas; > > probably because it's setting the validation off, but I don't know how > to > > control that. Anybody able to help me? > > > > Kalle > >
