I THINK this is similar to: https://issues.apache.org/jira/browse/CXF-2687
i haven't had a chance to look at it yet. If someone could create a small test case, that would be great. :-) Dan On Wednesday 24 March 2010 1:25:09 pm J. Aparicio wrote: > Hello. I have a wsdl which imports another wsdl, which I can not change. > That second wsdl imports some xsd schema, which in turn import another xsd > schema. Again, I can't change those xsd schemas (they are standard). > > The problem is the CXFServlet (through a Tomcat server) serves the first > wsdl, the second wsdl and the first xsd OK, but fails to serve the second > xsd. > The first xsd schema imports the second one via a line like this: > > <xsd:import namespace="http://www.w3.org/2005/08/addressing"; > schemaLocation="../types/ws-addressing-0805.xsd"/> > > The ../types/... reference is resolved OK on the filesystem, cxf's > wsdl2java has no problem with it. But it is inaccessible via the > CXFServlet. That means I can not give the CXFServlet url to implementors > of clients, because they can not get the second xsd schema. > > I've tried the command line wsdl2java and the maven plugin as well, with no > success on either. > > I don't know if it may have an impact, but I'm generating the code > including the "-noAddressBinding" option to wsdl2java. This is because I > have to extend the WS-Addressing classes, which otherwise come out as > final. > > I've tried CXF 2.2.5 and 2.2.7, Java5 and Java6, Tomcat5.5 and Tomcat6 > combinations, but all of them fail at the same point. > > What else could I try? > > Thank you :-) -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
